yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] byrko:
matr1x v14 shows 100% if battery is fully charged ;)
[Nexus S Android Development] morfic:
The charge is the same, it's just displaying a different % when the battery stops charging.

Putting make up on a zit doesn't mean the zit is gone, even if it looks better.
[Nexus S Android Development] djjonastybe:
I wonder how that 65fps thing can be the problem. Didn't know it even existed.

If ezekeel would like to make a kernel for every feature he puts into his kernel we can test everything separately.

Problem is I can test for reboots because I rarely call. So I don't have issues. Last time I had a reboot I remembered my settings 2 days ago :)

The only things that are left for me that can be the issue are:

lazy

100mhz

or maybe a feature i dont know of.
[Nexus S Android Development] IIIV:
What governor do you use?
[Nexus S Android Development] d_phekt:
Flashed 2.7 on Brainmasters MIUI ICS V2 on my i9020T last night and just now got a random reboot stuck on boot screen. Luckily i was able to reboot this time. I tried another kernel the other day and the same thing happened but couldn't boot past the boot screen and had to nandroid back to my previous setup. All stock settings in NSTools except BLN on. I love your work Eze, and have been a ritual user of your GB kernels, but way too many reboots and bugs with the ICS versions. It seems to me that all of the modified ICS kernels aren't playing well one way or another. At least I haven't found one. So once again back to trusty old GB MIUI I go.
[Nexus S Android Development] mobile_pc:
Thanks for an intelligible explanation :)
[Nexus S Android Development] krfoy:
it is because of Battery Life Extender Mod. You could install NSTools and change the setting.
[Nexus S Android Development] Mac Boy:
Battery %

It has nothing to do with Battery life extender and you will not get 100% on an Ezekeel kernel - he has mentioned an infinite number of times that it is only cosmetic. Approximately 96% on an Ezekeel kernel is equivalent to 100% on other kernels.
[Nexus S Android Development] d_phekt:
What is with the serious epidemic of battery OCD lately?
[Nexus S Android Development] IIIV:
No reboots for me during 5+ minute phone calls.

I'll report back in 24 hours.

Thanks

I9020T with Brainmaster's Stock ICS 4.0.3 + GLaDOS 2.8 (CFS / ondemand / 100% / 200-1200 MHz / Deep Idle: OFF)
[Nexus S Android Development] ale.landra91:
For me: deep idle on, 100-1200 mhz + live oc 5%, ondemand -> no reboot during call. Can somebody explain difference between top on and top off? I look in the thread but there are 10 answer...which is the correct one? I have only top on numbers never off

EDIT: second call it reboot

EDIT2: third call with same settings without live oc didnt reboot
[Nexus S Android Development] Tordp:
Exekeel, I have a problem with the proximity sensor not reactivating during phone calls. The screen also sometimes stays blank after the call is completed. I can't terminate the call in normal way and have to use the power button. This problem occurs almost half the time I make a call.

It seems like there is a problem with the proximity sensor input. When I use an app called AndroSensor I can test the sensor and see that it sometimes hangs activated (0 cm mode). I don't use Touchwake but I read in the thread that BUGFIX #2 had something to do with proximity sensor not reactivating the screen when making calls. Is there anything you can look up?

I don't have this problem with stock kernel or latest stable Netarchy. I'm using stock ICS with Deep Idle, Screen off max freq on, LiveOC off and BLN on.
[Nexus S Android Development] Po0yAn:
do u guys still have that annoying fade green color flashing after turning off the screen on ICS roms? it even exists on stock rom! how can i get rid of it?!
[Nexus S Android Development] :
lol :O i never had sth like that :)

Sent from my Nexus S
[Nexus S Android Development] ale.landra91:
With vodoo control plus use "reset to 2.3.3 settings"
[Nexus S Android Development] furiannn:
That still doesnt work for me with the green flashes. And the default gamma settings suck! Punchy is the way to go :)
[Nexus S Android Development] IIIV:
Try bumping up the min to 200 MHz. My speculation is that it's having trouble handling phone calls at 100 MHz.
[Nexus S Android Development] ale.landra91:
Ok ill try :) about deep idle is it normal that on stock rom now i have top on and top off number? For two weeks i had only top on.
[Nexus S Android Development] boostern:
With 200Mhz min no reboots so far.
[Nexus S Android Development] dirtywest:
reboot when playing music using winamp...
[Nexus S Android Development] ledzpg:
For those who are having reboot problems while in call, a question:

What's your launcher?

I was having no troubles with Trebuchet and NovaLauncher beta 5, but after changing to Go Launcher EX, I had a reboot during call and a monstrous slowdown after that.

I'm using the last CFS kernel published here on post #1946, with Powersave governor and Live OC 100% (100 ~1000MHz).
[Nexus S Android Development] justsignbythex:
By far the most stable version yet.

Tried 2.2-2.4, and had reboots while screen was off/standby.

So far on 2.7 for about 48 hours with no reboots! Everything is on stock settings with BLN on/blinking.
[Nexus S Android Development] layar:
Great kernel so far, installed on AOSP+ ROM by androiduser and works veeeeeery good, especially for deep idle
[Nexus S Android Development] rguz:
Just a little question, how should I know if deep idle is working? I enabled it and the stats for Deep idle-TOP off still shows zero. Thanks!
[Nexus S Android Development] Harbb:
Top off can be tested by turning Bluetooth on in the background or using GPS. If there is no background task going on it will top off. Only one of those states at a time.
[Nexus S Android Development] IIIV:
It's been 22 hours since I flashed this, and I extensively used my phone -- more than an hour (each): phone calls, Reckless Getaway (racing game), music (PowerAmp), and browsing, and watched a couple of minutes of Youtube videos; I even had a 10 minute phone call when the battery was down to 5% -- and so far, NO reboots.

I9020T with Brainmaster's Stock ICS 4.0.3 + GLaDOS 2.8 (CFS / ondemand / 100% / 200-1200 MHz / Deep Idle: OFF)

P.S. I will try and set Deep Idle: ON and report back tomorrow.
[Nexus S Android Development] caliban2:
Running the "official" 2.7 cfs for almost 80 hours now, perfectly stable. Only 2.3 had been similarly stable for me. Note that my only beef with ics plus glados were reboots during standby, no call reboots. Didle is working fine.

My config:

Stock-ics rooted; glados 2.7 cfs; lazy-gov; didle on; cpu 100-1000 mhz; max-freq screen off = on; bln on

Rest unchanged.
[Nexus S Android Development] maniac2403:
If you are using the powersave governor, you are bound to see slowdowns at some point because it essentially runs the cpu at lowest frequencies.

I alternate between ADW and Trebuchet.
[Nexus S Android Development] Po0yAn:
Then probably you own the i9023 model with slcd screen

It decrease the problem but doesn't solve it.and the colors are so washed out that makes u sick! I'm so used to my color settings on CM7.

Me and you sir are in the same league. Did supercurio update the voodoo colors for ics? Busy life doesn't let me to check the threads as frequent as bfore

neXus S i9020T - CM9 Kangs - GLaDOS v2.7 - 110/1320 MHz
[Nexus S Android Development] AeroEchelon:
Using NSTools, if either TOP=ON or TOP=OFF show some values other than zero then DEEP IDLE is working.

IDLE will produce values when you're actively using your phone w/ screen on.

TOP=ON will produce values if Bluetooth or GPS is running in the background

TOP=OFF will produce values when the the above is off and the phone is idling w/ screen off.

You want more TOP=OFF values than anything else. That means essentially all hardware that isn't required for minimal operation of your phone will be powered down. Simplistically, the only pieces of hardware that will remain on are your hardware inputs/interupts, cell radio, etc.
[Nexus S Android Development] marcell99:
Hello!

I'm new to this forum, but not new in modding android devices. After searching for good kernels I found GlaDOS and works perfectly. No reboots so far. The only thing is missing for me the LogCat. I read that it's included as a module, but how could I use it? It would be very helpful to my work.

And sorry for an offtopic question: what is BLN? I always read this word that "it works" or "BLN doesn't work". Thank you for your help!:)
[Nexus S Android Development] aLNG:
i teach u the best way to search using google

copy and paste this in google: site:http://xdaforums.com BLN
[Nexus S Android Development] Psych0Chimp:
From the chat in the Matr1x thread, it looks like mathkid has fixed the call reboot problem... In case you've not seen it.

Any chance of a quick 2.8 fix before you start playing with your Galaxy Nexus? ;)
[Nexus S Android Development] jurica_m:
Your answer is very stupid, this is his first question and your welcome isn't good.
[Nexus S Android Development] IIIV:
http://xdaforums.com/showthread.php?p=21038149#post21038149
[Nexus S Android Development] IIIV:
I have both of my Bluetooth and GPS off, and I'm only getting Idle and TOP=ON values.

I9020T with Brainmaster's Stock ICS 4.0.3 + GLaDOS 2.8 (CFS / ondemand / 100% / 200-1200 MHz / Deep Idle: ON)
[Nexus S Android Development] rentaric:
BT has to be off not suspended (turning off in settings = suspended), this is a ROM related thing not the kernel.
[Nexus S Android Development] IIIV:
Thanks for the info. Though, IIRC Ezekeel had Bluetooth turned off in his previous version (2.4 I believe) of GLaDOS. :confused:
[Nexus S Android Development] AeroEchelon:
Download ROM Toolbox from the market and create a script to kill bluetooth. This will kill bluetooth until next reboot.

echo 1 > /sys/class/rfkill/rfkill0/soft

Once you can confirm that you have TOP=OFF values, you can set this script to boot at startup.

P.S. Also endursa has created a flashable zip which you can flash in CWM to help with Bluetooth function with DEEP IDLE. However, if you don't use bluetooth at all, the script above should work just fine.
[Nexus S Android Development] bharadwaj1991:
Hello, I am using CFS 1.12 for Gingerbread/Oxygen Rom 2.3.2. It seems that lately when my phone is not used for a while (1-2hrs) and enters idle or deep idle. At this moment if i receive a call I will hear the ringtone loud...but when i answer the call i will not hear ANYTHING from the other end...they can hear me but I can not hear them. I have to hang up and call them back and everything is fine. I of course am only assuming this has something to do with idle or deep idle.

i don't know why i'm saying this as it seems Eze has stopped support for GB kernel...just wanted to let him know maybe this MIGHT be an issue for his ICS kernel...and a possible fix would be much appreciated.

thanks

b
[Nexus S Android Development] maniac2403:
I did not face any problems which you faced with the deep idle implementation which Eze did. Only problems I faced were phone reboots, which have vanished as well.
[Nexus S Android Development] marcell99:
Thanks. The 4th or 5th link was the way to the heven, but if BLN is just Back Light Notification than why couldn't you just write it down? Nevermind.

My other question was about logcat. How can i get it to work?
[Nexus S Android Development] Tordp:
GLaDOS 1.10 was the better choice for me when I had Oxygen 2.3.2. Perfect balance between speed, battery life and stability. The only difference between 1.10 and 1.12 is the Bigmem option. If your problem continues try install 1.10 and see if it helps.
[Nexus S Android Development] endursa:
please don't write such nonsense!

my patch doesn't disable BT completely, it just deactivates the BT suspende mode!

BT can be turned on and off as it worked in every other rom before ICS but the newly intruduced suspende mode, which only has the affect of breaking deep idle TOP=OFF and helps BT being switched on faster (1 compared to 4 secs).

so installing the patch does no harm to BT function!

But be aware that my patch is only for stock OTA update, not tested with any custom roms

It might work with the ones using the same framework!
[Nexus S Android Development] 93ae8074:
There is a thread explaining how to decompile framework-res.apk and how to recompile it again without troubles, so people using different ROMs can use that information to modify BT boolean parameter and fix BT issues with TOP=OFF.

I hope it helps.

BTW endursa, thanks for your time modifying framework-res.apk for us OTA ICS users.
[Nexus S Android Development] alienmind:
Just wanted to say that all my random reboots are gone since i flashed over stock ics instead cm9. Using 2.8 beta, no oc, deep sleep, bln and ondemand. Everything fine. Surprisingly all my deep idle stats go to top = off without patching framework (i don't use Bluetooth either)

Bln works fine except missed calls, but it can be fixed with neldar app or taker.

Good job Ez
[Nexus S Android Development] byrko:
Have you updated BLN today?
[Nexus S Android Development] AeroEchelon:
Sorry, personally I never use Bluetooth myself so I was never able to test out this function. Also, the only thing you explained in that post was:

Which I assumed disabled bluetooth.

Not a dev of any kind but thank you for a more thorough explanation.
[Nexus S Android Development] nexusphone:
If not enabling the useful MODs like LiveOC or Deep_Idle, we don't need to use custom kernels. Ezekeel must fix the "reboot bug", especially "while calling"
[Nexus S Android Development] renna1992:
yeah. he MUST fix it ... seriously guys? give the man a break after all he has done for us. i'm sure that there is a working fix coming by time but don't talk about any obligations from any developer here. they do it in their free time and we should be grateful that they share their work with us.
[Nexus S Android Development] IIIV:
Same here. Using version 2.8 CFS, ondemand, deep idle, and BLN. I don't notice any performance difference between 1200 MHz and 1000 MHz, so I'm just sticking with the latter to ensure stability. I had to flash endursa's BT disable zip to get Top=OFF working. 48 hours now and no reboot.

I would also like to add that GLaDOS 2.8 CFS with Brainmaster's stock ICS ROM gives the fastest and smoothest browsing experience, especially with content heavy sites, like http://google.com/news.
[Nexus S Android Development] nexusphone:
Indeed...

I beg you to forgive my rudeness.
[Nexus S Android Development] phone_user:
Pete fixed "Hot Bluetooth module"

https://github.com/peteralfonso/platform_vendor_pete/commit/a19d2a56ccf07b9ab53a44b7ba5605a1aaffd9e6

http://xdaforums.com/showthread.php?p=20917046#post20917046
[Nexus S Android Development] IIIV:
Not sure if I missed it, but did Ezekeel post a BFS of version 2.8?
[Nexus S Android Development] caliban2:
Nope, only cfs.

There isn't an official 2.8 anyway, just the two test versions.
[Nexus S Android Development] renna1992:
no problem, i just read a lot of those "hate-posts" recently :)
[Nexus S Android Development] Pix3l:
Hi, first of all thanks for your great Kernel. It's my first reply here so i hope i'm not making any mistake.

As i can understand the last posts (I'm french so maybe my understanding may be wrong) i'm not alone to get the same issue. I'm using the last AOSP+ v2.2 rom. Apparently my phone does work with the stock kernel used in the rom, but when i flash it with Glados 2.7 my phone reboot randomly when i'm making a call. Moreover i have many missed call.
[Nexus S Android Development] IIIV:
I'm not sure if Deep Idle has anything to do with reboots, but I tried these settings:

ondemand / 100% / 200-1200 MHz / Deep Idle: ON (Top=OFF working) / stock voltages

...and my battery was down to 10%. While my phone was in Deep Idle, I tried calling it and it just turned off. I tried turning it back on, but it wouldn't; so I had to pull out the battery and then turn it on.

I didn't have any reboots with excessive use for 48 hours with the same settings above, but with Deep Idle: OFF.
[Nexus S Android Development] Pix3l:
Okay, thanks i'm going to try this.
[Nexus S Android Development] thegtfusion:
if I set live OC to 110% at what should i set my voltages? increase the arm voltages with 25mV?
[Nexus S Android Development] mixtapes08:
If your having reboots raise arm by 25mv across the board.

Sent from my 1st android phone Nexus S
[Nexus S Android Development] thegtfusion:
all the arm voltages?
[Nexus S Android Development] ledzpg:
Yeah, sure.

But the slowdown was REALLY sloooooow... hehehe :p

Anyway, I've updated the ROM to the new AOSP+ and everything is working ok since 01/06/12. :cool:

I've tried to use Go Launcher, but since I can't (or just don't know how to) hide that annoying "home-button-bar" below apps on appdrawer, I'm back to Trebuchet.
[Nexus S Android Development] ozone89:
Sir, great kernel, but somehow it seems it broke the music app on cm9 ?_?
[Nexus S Android Development] IIIV:
Did you wipe /cache and Dalvik cache before flashing the kernel?
[Nexus S Android Development] TheLastMirana:
is this rom stable such as matr1x?

i want to give this a go for 2morrow but dont have much time for testing/ tweaking.

Just want to see the battery life and performance increases. Also deep idle works i presume?
[Nexus S Android Development] civicdrivr:
I tried 2.7 cfs today but kept getting reboots when on a call for more then 3 minutes. Flashed back to 2.4 cfs

Live oc - 105, 1260max 420min

Deep idle off (I get reboots with it enabled)

On demand governor

Voltages bumped up 25mv

Sent by carrier pigeon
[Nexus S Android Development] vis80k:
how does the battery performance feel for you using 2.7?

my experience is that it feels it drains a little too fast, compared to Eugene's.

using stock settings as provided by the kernel.
[Nexus S Android Development] ciwek90:
can i use this on STOCK? and will this kernel replace ics boot animation?
[Nexus S Android Development] renna1992:
yes you can. and yes. if you don't want the boot animation which comes with the kernel then delete the media folder inside the zip :)
[Nexus S Android Development] caliban2:
Those of you running a test build and having tested 2.7 seriously (!) before: worth the upgrade, performance-wise?

2.7 cfs is stable for days now, so only performance would be a reason for me.

Why "seriously tested"? changing clock speeds and voltages on more or less stable custom-roms and then report restarts/freezes, blaming the kernel?! Please go away...
[Nexus S Android Development] IIIV:
I9020T with Brainmaster's Stock ICS ROM + GLaDOS 2.8 CFS / ondemand / 200-1000 MHz / Deep Idle: OFF / stock voltages

P.S. I notice that I have two slight increases on my battery graph, even though I didn't charged my NS. I guess I'm gonna need to calibrate my battery.
[Nexus S Android Development] Ezekeel:
I have read the last X pages of feedback and still have no clue what could cause these reboot problems.

Therefore I compiled a whole slew of test kernel with one feature systematically disabled after another. Start at the top with step0 and if you are having reboot problems move to next step with some feature removed. Go on until you have reached a stable version and let me know which step is stable for you.

step0:

CFS 2.7 + small fix compiled with Google toolchain

http://www.multiupload.com/I8O2JE1V1V

step1:

- min freq 200MHz when GPU is active disabled

- 65fps display

http://www.multiupload.com/2J8Y1OSCTH

step2:

- live oc

http://www.multiupload.com/P44Y62K1GU

step3:

- bigmem

http://www.multiupload.com/AUAVXTSBSB

step4:

- touchwake

- bln

- bld

- custom voltage

http://www.multiupload.com/3GC2HD2U1C
[Nexus S Android Development] civicdrivr:
I flashed CM9 A20 last night along with 2.7cfs. Ive been using my usual 1260/210, LiveOC at 105, with deep idle on, and I havent had a reboot. The only issue Ive run into was a non responsive black screen when on a call, but thats not a constant. It only happened three times, Ive made about 8 calls or so.

EDIT - I take that back. I was on the phone for about 15 minutes just before and it rebooted. Ill try out the different kernels you posted.
[Nexus S Android Development] eezak:
These ones kill wifi
[Nexus S Android Development] xjerlzx:
lazy

but i have change to use eugene kernel. its didle saves more battery then deepidle amazingly..
[Nexus S Android Development] phone_user:
Step1, reboot while calling

From Step2, No reboot while calling

maybe recent issue due to Live OC? But Matr1x v14 does not have the issue though it also has Live OC

EDIT : wifi disabled on test kernels
[Nexus S Android Development] possebom:
No wifi in step 0, dmesg output :

<4>bcm4329: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
[Nexus S Android Development] kramer987:
don't know if its the Nova launcher I just installed or the upgrade from glados 2.5 to 2.7 but my phone works absolutely flawlessly and I experience no lag at all. many thanks
[Nexus S Android Development] IIIV:
Is it just me or my NS gets literally hot when using Live OC (I just tried 110%)?
[Nexus S Android Development] DarkhShadow:
My CPU gets hot when I'm playing games on charge, but I had that on stock as well soo.....

Sent from my ice cream powered Nexus S
[Nexus S Android Development] mobile_pc:
Please discuss the problem with mathkid. Matr1x has all your MODs, but no reboot while calling
[Nexus S Android Development] flodb113:
Had GLaDOS version 2.4, and since then I've tried Matr1x v14, and Speedy-3 from eugene. Then I remembered why I first tried this kernel, and realised it was for deep idle, just to see what everybody was talking about. So now on version 2.7 I'm back on GLaDOS. No OC, Deep Idle on (and working just fine), other than that, nothing else was modified. Didn't have a reboot so far, but I only had one 25 minute call, so I'm still testing. It's great so far, I'm loving this kernel!
[Nexus S Android Development] michalurban:
Help for a newbee

Hi,

I`m not entirely new to android and nexus s, but I`m curious. Since some Glados version 2.0, I`m interested in it and checking this thread every now and then. But always, no matter the version, I run into many ppl without problems and few with reboots. It was with every versions here. Can somebody please describe me what the situation is now? As I again see reboot problem discussion ...

Thanks and sorry for the kinda lame question ... :)
[Nexus S Android Development] phone_user:
I'm flashing

---------- Post added at 09:24 AM ---------- Previous post was at 09:11 AM ----------

unfortunately, reboot while calling :confused:

I'll send last_kmsg to you
[Nexus S Android Development] shubu000:
can confirm that i got reboot while calling on 2.8

live oc 110

deep idle on

screen off max freq on

governor lazy

freq: 220-1100

thanks for your continual development ezekeel
[Nexus S Android Development] noobiekins:
I honestly can say i have had any reboots while calling, using 2.7 BFS, 2.8bfs soon. Note, if you use liveoc, you have to adjust the voltages too. Too low of INT voltage will cause a non responding crash or reboots,too low of arm voltage causes random reboots. Too high gpu overclock will result in artifact freeze into reboot.

My settings on 2.7 BFS. Stable for me, over 80 hours no reboot of any kind.

Governor:Lazy

Min:110

Max:1100

LiveOC:110%

DeepIdle:ON

ScreenOffMaxFreg:Off

Voltage order: ARM voltages first, INT voltages second.

1000mhz(1100mhz):1275mv 1000mhz(1100mhz):1100mv

800mhz(880mhz):1175mv <--- Increase to 1200mv if necessary 800mhz(880mhz):1050mv

400mhz(440mhz):1025mv 400mhz(440mhz):1050mv

200mhz(220mhz):900mv <--- Increase to 925mv if necessary 200mhz(220mhz):1050mv

100mhz(110mhz):875mv <--- Ignore if your min is 220mhz 100mhz(110mhz):950mv

Edit: Could anyone tell me what exactly is INT voltage? I believe it's related to the gpu voltage but I'm probably wrong.

Edit2: This is undervolted for the most part if anyone didn't know.