yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Ezekeel:
I have checked the code several times now and cannot find any further bugs. Also, I am running with an OC value of 120 and DEEP IDLE enabled and never had any reboot problems.

So my guess is that the people still having reboot problems either use a ROM with bugs or some OC value which is not stable on their device or with the current voltages.

I would recommend that you make a clean install and use the official OTA ROM. Make a factory reset before that and format /system and /boot, then install the ROM, then install GLaDOS, then superuser. Do not install any apps yet. Try if everything runs stable for a longer time until you are sure everything works fine. Then add one app after another.
[Nexus S Android Development] :
Very peculiar, eh? I've been using 2.7 CFS with AOSP+ 2.2.5 and haven't had any problems kernel-related. My longest calls are 24 minutes, 30 minutes and 33 minutes - didn't have any issues. Maybe I just haven't tested long enough.

running Interactive 1200/200 default kernel voltages with deep idle ON

Thanks for your work!
[Nexus S Android Development] mobile_pc:
You did not use Live OC :(
[Nexus S Android Development] mobile_pc:
I have the greatest respect for you, but it's not. "using only stock rom"?!

Here, we are in XDA...
[Nexus S Android Development] suksit:
He just want to prove that if using stock ROM results in no reboot then it's ROM-related issue, not the kernel issue.
[Nexus S Android Development] gonintendo:
I've been on 2.7 for about a week to two weeks and I haven't had a single reboot. I don't have an oc though.
[Nexus S Android Development] mobile_pc:
Though Matr1x has all Ezekeel's MODs, no reboot while calling with enabling LiveOC. Ezekeel'd better ask mathkid what he did. I think devs should give help between them.
[Nexus S Android Development] shubu000:
i can now report that it seems i can get a liveoc of 110 to workk during calls by upping all internal voltages.

sorry that i didn't change this earlier, however i got 110 live oc working on gingerbread without changing anything, so i was under the impression that it is the same for ICS....
[Nexus S Android Development] 1125you:
Liveoc 110

Lazy

default voltage

No deep idle

No reboot problem while calling since glados 2.4

Hmmm..
[Nexus S Android Development] eezak:
Using Glados 2.8, no oc, deep idle is on with ota rom, almost immediate reboot while playing music trough bluetooth when screen goes off.

Edit2: Stock music app crash too when screen goes black.
[Nexus S Android Development] navjottomer:
Was using Matrix kernel before and now switched to Glados 2.8 , rockstable with live oc 108% and stepping upto 1512Mhz.
[Nexus S Android Development] Lazat:
Do you mind sharing your arm- and int-values to get liveOC stable at 120% :) ?

Nexus S i9023, CM ICS alpha 18, mathkid 13.0 bfs, 115% LiveOC, 230/1150. deepidle off.
[Nexus S Android Development] flodb113:
+1
[Nexus S Android Development] caliban2:
Thanks for 2.8, appears to be stable and smooth. :-)

I think you're right about the rom-cause when it comes to restarts during calls. Also it's just dumb when testing for general stabiliy while at the same time overclocking cpu and gpu.

There has been some trouble in code though, when it comes to restarts during standby. Only 2.3, 2.7 and now 2.8 didn't give me those. Looks like you nailed it though, 2 versions in a row point to that.

If this is stable for another day I can finally think about oc and undervolting. :-)

edit:

these are my settings in nstools, you can see it's pretty much stock.

echo 0 > /sys/class/misc/backlightdimmer/enabled
echo 5000 > /sys/class/misc/backlightdimmer/delay
echo 1 > /sys/class/misc/backlightnotification/enabled
echo 0 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 750 > /sys/class/misc/backlightnotification/blink_interval
echo 600 > /sys/class/misc/backlightnotification/max_blink_count
echo 96 > /sys/class/misc/batterylifeextender/charging_limit
echo 1 > /sys/class/misc/deepidle/enabled
echo 0 > /sys/class/misc/touchwake/enabled
echo 45000 > /sys/class/misc/touchwake/delay
echo lazy > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1 > /sys/devices/system/cpu/cpufreq/lazy/screenoff_maxfreq
echo deadline > /sys/block/mtdblock4/queue/scheduler
echo deadline > /sys/block/mmcblk0/queue/scheduler
echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Nexus S Android Development] SwatMaster:
+1

Don't think it's related to GPU, since that frequency (1Ghz) is too high.
[Nexus S Android Development] IIIV:
Had 2 reboots while screen off last night with BFS / ondemand / 110% / 220-1100 MHz / default voltages.

So, I lowered down to 105% / 210-1050 MHz / default voltages, and no reboots so far and seems more stable. I'll be using my I9020T extensively today and report back tonight.

Thanks for the update, Ezekeel.
[Nexus S Android Development] ChargingPaladin:
Ezekeel, what do you keep your process limit at? I was up for 92 hours with standard, less than 4 hours after switching to no-more-than-4.

Sent from my Nexus (IC)S
[Nexus S Android Development] Thomazzanten:
Hmm, 2.8 seems to kill wifi. Reboots are gone so far though
[Nexus S Android Development] caliban2:
wifi is fine here.

Unless you're using one of the test-versions (step0...) which did break wifi, it's you...
[Nexus S Android Development] got2best:
2.7 no reboot for me.... 2.8 setting the same as 2.7 no live oc 200-1200 reboot in calls on 2.8:/
[Nexus S Android Development] flodb113:
2.8 breaks wifi, luckly for me I had a nandroid made just before flashing it. Back on 2.7.

Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
[Nexus S Android Development] IIIV:
No Wifi issues for me with v2.8 BFS.

I had a reboot during a phone call at around 2 minutes with these settings:

ondemand / 105% / 210-1050 MHz / default voltages

Now trying: ondemand / 120% / 240-960 MHz / +25 mV arm and int voltages and no reboot during a 5 minute phone call. You guys should try these settings and let us know your experience. I'll report back mines in 24 hours.
[Nexus S Android Development] technogravy:
No issues in wifi for me too, but reboots on calls. Turned of loc and no more reboots. Battery life isn't the best. But will test some more on the latest cm9. Currently tested on asop +
[Nexus S Android Development] shubu000:
i got 110 and 120 working at one stage, and they both pass the initial 5 minute call test, but both failed later on

for a live oc of 110, i had a reboot a few hours later in a call

for liveoc of 120, i had a sod for a few hours before i realised it

i kinda just resigned to go without liveoc, since deepidle's magnificent
[Nexus S Android Development] AeroEchelon:
Since Ezekeel believes this is a ROM related issue, if you're going to post success w/ no reboots, could you guys please post how much hours of uptime and the ROM that you're currently using? Maybe we can see a pattern. Thanks.
[Nexus S Android Development] veagles:
Can someone explain the accuracy of deep idle stats?

How long after they need to be reset?

My phone has been idle on battery for 3 hours, and its been in deep idle with top off for just 10 mins as per the stats.
[Nexus S Android Development] michalurban:
Battery

Hi, as I`m not interested in OC, only in battery life (via deep idle), do I understand this right:

I use stock ICS ROM. Rooted. I install this (Glados 2.8) kernel and thats it. Deep idle should be up-and-running from the start, saving the battery. Right?
[Nexus S Android Development] caliban2:
No.

Get nstools from market and activate it.
[Nexus S Android Development] SPVlover:
@michalurban well i guess u should simply install NS tools (free on android market) and then configure everything to your likeing.

Deep idle is OFF by default.

NS tools will show u statistics of didle usage once activated.

C ya
[Nexus S Android Development] endursa:
since i had no reboot issue on my i9020 on 2.7, but i switched to my i9023 yesterday i have them now on the i9023 with 2.8

Situation:

Both phones run the same rom/kernel combination, live oc and same settings:

Rom: AOKP m2/AOKP m2

Tweaks: - both the same

BLD: ON (2sec)

BLN: ON (no blink)

BLX: 96 %

Touchwake: OFF

IO: deadline

CPU: ondemand 100/1000MHZ

Live OC 100%

DeepIDLE: ON (bt patched framework)

Idle status shows TOP=OFF usage

No Custom voltages

I just made 4 phone calls,

first one, i received a call, reboot after about 2-3 minutes into the call,

second i received an other call, about 1-2 minutes long, no reboot,

set CPU: ondemand 200/1000

third call, called carrier hotline for about 2 minutes, but i only listened, no reboot

fourth call, called out, reboot after about 2-3 minutes!

i honestly think it could be a problem that only occurs on the i9023 model, but at least til now i have no clue where it comes from, maybe it's the rom AOKP milestone2?

i'll try now with calling my local Time number, and test if reboots are reproduceable! if i find any patterns i will report back!

PS: ezekeel i tried your step0-step4 kernels, but they break wifi unfortunately :/
[Nexus S Android Development] caliban2:
it certainly isn't related to the 9023 model itself. I never had a call reboot using stockrom, just reboots during standby. Those were kernel-related but seem to be fixed since 2.7
[Nexus S Android Development] got2best:
I am running fuzz's kangs and no rebooted with 2.7 cfs I am on a 9023 and also when I put 2.8cfs same rom reboots durring phone calls after about 2 min
[Nexus S Android Development] IIIV:
Tried these settings last night:

ondemand / 120% / 240-960 MHz / Deep Idle: ON / +25 mV arm and int voltages

Results:

- No reboots during phone calls

- Reboot on screen off while playing music (PowerAmp)

So, I decided to try the same settings but with "Default voltages" option checked.

Results:

- No reboots during phone calls

- No reboots on screen off while playing music (left it playing a 20-track album as I slept last night)

I9020T with Brainmaster's Stock ICS ROM + GLaDOS 2.8 CFS
[Nexus S Android Development] veagles:
I just had a reboot in standby with glados 2.8 cfs on peter alfonso's rom. Never had any reboots before.
[Nexus S Android Development] IIIV:
You might want to state what phone you have and what settings you use.
[Nexus S Android Development] endursa:
some first test results

first call: no reboot after 5 minutes

second call: reboot after 2-3minutes	http://pastebin.com/Rtfwiyda

Begin test series I - 13.01.2012 - done by Endursa on i9023

#ROM: AOKP_Milestone2,

#KERNEL: GlaDOS 2.8,

#SETTINGS: BLN,BLD(2sec),DI:ON,ondemand,200/1000,display autooff(1min),

#Conditions: no proximity interaction, phone on table, just dailed time number

first call - 16:47:40

16:50:20 reboot - last_kmsg: http://pastebin.com/KCDDheSj

call time: 2min 40sec

second call - 16:55:00

no settings changed

16:57:50 reboot - last_kmsg: http://pastebin.com/mE9myVZX

call time: 2min 50sec

third call - 17:02:10

no settings changed

17:03:10 display off

17:09:00 reboot - last_kmsg: http://pastebin.com/NdB7hZWg

call time: 6min 50sec
[Nexus S Android Development] flodb113:
One small noob question. How did you logcat? Because with adb I get:

Unable to open log device '/dev/log/main': No such file or directory
[Nexus S Android Development] veagles:
I9023 running Peter Alfonso's ROM 01-12-12

TouchWake : Enabled

Deep Idle : Enabled

Everything else defaults.

---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------

You need to insmod /system/modules/logger.ko in an init.d script
[Nexus S Android Development] endursa:
for last_kmsg just do

su

cat /proc/last_kmsg > /mnt/sdcard/last_kmsg.txt in terminal app or adb!

edit: i gonna start testing with glados test series tomorow, cause i gotta go to a birthday later!
[Nexus S Android Development] flodb113:
Thank you @veagles and @endursa.
[Nexus S Android Development] endursa:
did a little more test, since had some spare time

#ROM: AOKP_Milestone2,

#KERNEL: GLaDOS-cfs-step1

step1:

- min freq 200MHz when GPU is active disabled

- 65fps display

#SETTINGS: BLN,BLD(2sec),DI:ON,ondemand,200/1000,display autooff(1min),

#Conditions: no proximity interaction, phone on table, just dailed time number

#Wifi not working with this kernel but disabled while testing anyways!

first call - 17:31:40

17:46:40 no reboot

call time: 15min

second call - 17:48:10

18:03:10 no reboot

call time: 15min

third call - 18:04:00

18:10:00 no reboot

call time: 6min

i think i have found a winner :)

since i used 200/1000 also before with 2.8, the trouble could be coming from the 65fps, despite i can't imagine why :D

the only problem is i can't use this kernel as a daily driver, since it breaks my wifi :(
[Nexus S Android Development] nexusphone:
reboot while calling due to LiveOC

hope that fixed, cheers!
[Nexus S Android Development] endursa:
i don't understand what you wanted to tell us, if you wanted to give me the advice, i have to tell you, i don't use live oc at all!

---------- Post added at 06:23 PM ---------- Previous post was at 06:16 PM ----------

quoted from steve garons kernel thread on the topic of voodoo colors and the 65fps hack, i think since the hack also causes the trouble with the green screen flicker on the amoled displays, it would be good to remove this "tweak"/hack :)
[Nexus S Android Development] morfic:
Deep idle is only used.when something prevents it from entering deep sleep (the state we really want)

Best example is music playback where busy time and idle time alternate.

In this state where you keep phone from deep sleep, deep idle, a previously unimplemented power state the SoC a supports, you save power over staying in normal idle.

If it sits on desk, not doing any such work for you, SoC belongs in deep sleep, sounds everything works normal for you.

Excessive deep idle time when nothing was supposed to be going on is actually a sign of an unresolved.issue.

You though are ok.

Hope this helps.
[Nexus S Android Development] Ezekeel:
I compiled a CFS test kernel for people with reboot problems without the 65fps display frequency tweak which could be responsible for the problems.

Download: http://www.multiupload.com/LWWE00DR7Q
[Nexus S Android Development] veagles:
Thanks morifc for that clear explanation, I finally understand deep idle.

Sleep > Deep Idle > Idle

So, battery usage would show my phone as awake when its in deep idle, correct?
[Nexus S Android Development] morfic:
You will find a low deep sleep number if you do engage your phone in activities that benefit from deep idle.

I have not seen an app actually accounting for deep idle time.

I mean avg stats tools, not ns specific tools including TOP ON/OFF time that Ezekeel collects.
[Nexus S Android Development] phone_user:
On this test kernel, reboot while calling

/proc/last_kmsg

last_kmsg
[Nexus S Android Development] IIIV:
Working great so far. Played music (PowerAmp) while screen off for about an hour, a couple of 5+ minute phone calls, browsed Engadget and ESPN, watched YouTube videos (app), and played Reckless Getaway (racing game) -- NO REBOOT.

My setup:

I9020T with Brainmaster's Stock ICS 4.0.3 + GLaDOS 2.8+ CFS / ondemand / 120% / 240-960 MHz / Deep Idle: ON (Top=OFF working) / default voltages (kernel)

Thanks, Ezekeel!
[Nexus S Android Development] ragnarokx:
You should review the forum rules - your thread belongs in the General section:

A benchmarking thread does not fall into any of the above categories. Research and development is for developers who are working on/towards a project, creating something.
[Nexus S Android Development] endursa:
nice made 3 phonecalls today, 3 minutes 6 minutes and 56 minutes and no reboot, on the test kernel !

settings are the same as in my tests from yesterday! no live oc or UV but also no reboot on phonecall :)

i don't know why the 65fps hack interferes with phonecalls, but at least for me i can say its stable :)
[Nexus S Android Development] ragnarokx:
I'm glad you can see it that way. If sticky is your goal, you have a much better chance getting it stuck in General than in Development. I've never had any use for benchmarks personally, but I do commend your thoroughness and organization.
[Nexus S Android Development] djjonastybe:
Does anyone know if I can build the glados github?

Maybe someone can explain me how so I can mess around and hopefully improve a few things where possible :)

But it's not up to date I think.

Well as far as I'm concerned about the forum moderators. These forum moderators have the strangest ways of thinking... They are irritating me all the time moving my posts. Sometimes their logic makes no sense. Example given: when posting something related to development, they move it to the Q&A area because it's a question.

While my thread is in the development category, i get thousands of answers, and in the Q&A I never get an answer.

I think we should have a development category and a releases/download category to make our posts.
[Nexus S Android Development] Pitrino:
i've too reboot with fuzz
[Nexus S Android Development] IIIV:
After 18 hours of extensive use (music, phone calls, browsing, YouTube, Reckless Getaway racing game), over 5 hours of Android OS keep awake, and no reboot...

I9020T with Brainmaster's Stock ICS 4.0.3 + GLaDOS 2.8+ CFS / ondemand / 120% / 240-960 MHz / Deep Idle: ON (Top=OFF working) / default voltages (kernel)
[Nexus S Android Development] ataranea:
So im also reading that people are getting similar problems as me. When i talk on the phone for about 2 mins, my phone reboots itself. It's happened everytime i've tried to talk on the phone. Anyone know what is up with this? I have the androiduser rom on the nexus s 9023
[Nexus S Android Development] IIIV:
Nobody can help you if you're not going to post what settings you're using or your /proc/last_kmsg
[Nexus S Android Development] Ezekeel:
If you are still having trouble with reboots see if the issues also appear on this minimum barebone CFS test kernel.

Download: http://www.multiupload.com/GQKHRFI54R
[Nexus S Android Development] phone_user:
no reboot while calling on step0

in reverse order to http://xdaforums.com/showthread.php?p=21252387#post21252387 ?
[Nexus S Android Development] h46it:
Today I had a reboot on 9020T running AndroidUser00110001 2.2.5 ICS rom. I just installed 2.8 lastnight till this morning i didn't have a problem at all. Half way through my day at work, I had a random reboot. I didn't think too much of it, so I just pulled the battery and gave it another try.

Now 4hrs later and the phone will not boot still (stuck on boot screen). I've tried to flash the test cfs build on the last post by Ezekeel, and still no luck. I've tried flashing the latest from AndroidUser00110001 2.3 and no luck. I was running the stock kernel from AndroidUser00110001 2.2.5 and never a problem till I flashed 2.8 BFS. I think i have to wipe the phone now :(

My settings on the phone were:

1.2Ghz

Ondemand Gov

Deep idle on

no live oc
[Nexus S Android Development] IIIV:
@h46it Try v2.8 CFS or the v2.8+ CFS test kernel. I didn't experience any reboot with either one of them.
[Nexus S Android Development] h46it:
It's too late...I've wiped...:(
[Nexus S Android Development] stewarta:
Wipe

I think your problem is to do with where you are coming from in terms of previous ROM/kernel combos and not wiping. See http://xdaforums.com/showthread.php?t=1397358&page=5 but if coming from a different ROM, then a full wipe is needed: Wipe boot, system, data, cache, Dalvik cache. And do NOT restore system from Titanium Backup ... just the apps.
[Nexus S Android Development] h46it:
Why am i wiping if i'm just flashing a kernel? I wipe davik cache before i install any kernels. When i do install a ROM I wipe everything. Not using Titanium backup as it's causing problems with market.
[Nexus S Android Development] stewarta:
All good then ... but also wipe Cache (download cache) in Recovery.
[Nexus S Android Development] Ezekeel:
I have compiled a new round of test kernels building on the barebore CFS test kernel step0. Each step adds one tweak and has all the tweaks added in the previous steps.

step1 + Voodoo Color

step2 + Voodoo Sound

step3 + Lazy + made default

step4 + BLX

step5 + BLD

step6 + BLN

step7 + Touch Wake

step8 + Live OC

step9 + Custom Voltage

step10 + Deep Idle

step11 + Bigmem

step12 + 200MHz limit GPU on

step13 + 65fps display

step14 + WiFI PMFAST

Download: https://spideroak.com/browse/share/ApertureScience/Tests
[Nexus S Android Development] mobile_pc:
Ezekeel, faithful dev!
[Nexus S Android Development] phone_user:
From step7, reboot while calling!

maybe due to Touch Wake?
[Nexus S Android Development] aLNG:
other steps u dont have reboot?
[Nexus S Android Development] phone_user:
step0 ~ step6, no reboot
[Nexus S Android Development] IIIV:
Still going... Loving the Deep Idle...
[Nexus S Android Development] Ezekeel:
It seems like it. I will wait for confirmation from other testers.
[Nexus S Android Development] KalimochoAz:
It seams extrange since I have no touchwake on my kernel and some users are also complaining about this issue.
[Nexus S Android Development] endursa:
in will test the series when i get home sometime later this evening

Gesendet von meinem Nexus S mit Tapatalk
[Nexus S Android Development] markovianmind:
where is the version for GB?
[Nexus S Android Development] michalurban:
Version for GB

There is none ...
[Nexus S Android Development] phone_user:
V1.12, the last version for GB

glados-cfs-1.12.zip

glados-bfs-1.12.zip
[Nexus S Android Development] michalurban:
Sorry

Sorry, my bad, I didnt mention this version because its so lower version numbe ...
[Nexus S Android Development] ziouf:
hello

First I would like to say I love your work on this kernel.

But I have a little bug with BLN.

For example, I have a notification.

Back light is blinking. So i turn on the screen and after the unlock, back light turn OFF. But it should stay on.

Is it a known issue ?

Regards

Edit :

Kernel: Glados 2.8

Rom : AOSP+ 2.3
[Nexus S Android Development] SwatMaster:
Yeah it is, at least for me.
[Nexus S Android Development] got2best:
Sorry I have a a noobish question.. I don't understand.. this I thought that when I install the stock ICS rom.. that deep idle top off would work.. but I still only get top on stats.. thanks in advance for anyone that can help or explain :)
[Nexus S Android Development] y3mita:
Deleted
[Nexus S Android Development] nathanson666:
Reboot on call

I'm running CM9 A20p1 with Glados 2.8 BFS. No live oc and stock voltages.

When I had the max frequency set to 1000MHz I had no reboots during calls but when I set the max frequency to 1200MHz I got a reboot right away in a call.

Note: It seems like the 1200MHz step is stable otherwise. No reboots in games of video watching.
[Nexus S Android Development] endursa:
Begin Test series III - 16.01.2012

#Phone: i9023

#ROM: AOKP_Milestone2,

#SETTINGS: BLN,BLD(2sec),DI:ON(bt patched framework),ondemand,100/1000,display autooff(1min),

#Conditions: no proximity interaction, phone on table, just dailed time number

#KERNEL: GLaDOS-cfs-step14

first call - 16:50

reboot 16:55

call duration 5mins

#KERNEL: GLaDOS-cfs-step13

first call - 17:09

no reboot for 20 mins

second call - 17:30

no reboot for 10 mins

third call - 20:38

reboot after 1min

#KERNEL: GLaDOS-cfs-step12

first call - 20:45

no reboot for 5 mins

my results so far!

but i cannot tell if step 12 is stable, at least not from one 5min phone call!
[Nexus S Android Development] IIIV:
With NSTools, turn off Backlight Dimmer.

http://xdaforums.com/showthread.php?p=20935218#post20935218
[Nexus S Android Development] SwatMaster:
It's already off...
[Nexus S Android Development] got2best:
Anyone able to help me with this?
[Nexus S Android Development] att1cus:
Check 2 posts up.

From IIIV:
[Nexus S Android Development] phone_user:
http://xdaforums.com/showthread.php?p=20917046#post20917046

the patch for the stock rom (the OTA 4.0.3 IML74K) by endursa

http://xdaforums.com/showthread.php?p=20935218#post20935218
[Nexus S Android Development] ziouf:
i already turned off dimmer

But no change