yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] franciscofranco:
Yeah I've seen that.

I've been testing a lot this past few days and after I disabled deep_idle I never ever ever had any connection drop, either data, gsm or wifi. I tried with CFS, BFS, CFS-ICS, with Oxygen, Devnull and ICS by Koush, none of that causes unexpected behavior of data/gsm/wifi drops. And considering I've seen a good amount of users complaining about that in Glados thread, I'm starting to guess the problem might be really with deep_idle since it's the only constant around here. Not saying deep_idle is bad, quite the contrary I love it, but it's not bullet-proof, and about that issue my money lies with deep_idle.
[Nexus S Android Development] polobunny:
For what it's worth no matter what settings I use I've never seen my phone run deepidle for more than 2 days without my phone crashing. I'm starting to think some phones just aren't compatible or some people don't care about stability/they reboot their phones often. I'm gonna switch back to glados soon to see if it's stable, but I'm not necessarily putting any money on that.
[Nexus S Android Development] phone_user:
deep_idle... consistently, a red-hot issue
[Nexus S Android Development] laidick:
disable using NSTools
[Nexus S Android Development] LionAR10:
+1 to data failure with deep_idle.

Happens at least once a day for me, often more. And with data failures come GV outbound calling failures ...
[Nexus S Android Development] hilton502:
nstools just can set led dimmer，it can‘t disable the led

i want to reduce the brightness
[Nexus S Android Development] SA-07:
Yoyo Franco,

I need ur help...this is with my kernel on Ics

If I press the power button I get a green screen and a reboot..

Have u ever gotten this and if u have what was the code fix?

Ty
[Nexus S Android Development] hachoo:
Using the 11/17 Kernel CFS with NSCollab .50. Getting some really good results when using Lazy (1050/105), LiveOC 105, ScreenOffMaxFreq ON and Deep Idle OFF. UV 900mV on low clocks.

So far got 2 Days with 30% battery left. Used Google Maps, Facebook, Net and updated using Market all on 3G. The only anomaly was at 40% battery, it wouldn't load GoSMS and the msgs for some reason. Crashed the app but was fixed after restarting. Otherwise, the kernel/ROM combo is quite snappy and no real lag as yet.
[Nexus S Android Development] vis80k:
Isn't maxfreq to enhance deepidle so deepidle is entered asap?

Does it help with battery even with deepidle off??
[Nexus S Android Development] 93ae8074:
It does not help with battery without Deep-Idle.

Cheers.
[Nexus S Android Development] vis80k:
funny thing is, first the quote is from my comment, and second is I had the drops with deep idle off...
[Nexus S Android Development] frenccw:
I haven't had any connection loss since switching to glados with deep idle enabled for 2 days though. I guess it just doesn't play nice with certain combinations with roms, kernels and phones
[Nexus S Android Development] Zorrich:
I totally agree. I very rarely reboot my phone unless I have to. I also am very picky when it comes to stability. I personally will not accept any radio dumps or connection problems on a mobile phone. The whole point of the phone is to ensure people can always get in touch with me.

I am still running the November 17 kernel, and I haven't lost my connection once, nor has my phone rebooted. Also, I haven't had a single weird bug of any sort. I did have to disable deepidle to get this stability.

I had planned to try out glados to see if I could run deepidle, but if others are still having the issue, I'm sure I will too. Going to stick with what works :)
[Nexus S Android Development] hachoo:
Ah really? ah well..... hahahah! I'll turn it off then!
[Nexus S Android Development] franciscofranco:
Thanks for the report.
[Nexus S Android Development] some_random:
you beat me to it......

was going to say the same thing been running glados 1.8 for about 2 days now.. see report to see exactly what I was running a couple of pages back no data loss at all with deep idle on

so not sure whats going on now i'm confused :\
[Nexus S Android Development] ro_explorer:
Well, I didn't had any conenction drops (either 3G or WiFi) since I've turned off the deep_idle ... 40 hours uptime w/o issues :).
[Nexus S Android Development] SA-07:
Yo

Didja see my q?
[Nexus S Android Development] caleb1783:
I have something contrary to report.

i was on deep idle for last few days...

with settings according to my signature...

i had no problems until yesterday when my phone had SOD...

so i decided to turn off deep idle and maxscreenoff...

then today, i had better battery life... but also had 3g data dropoff...

strange.
[Nexus S Android Development] franciscofranco:
Never seen that before. Change to stock voltages and see if it fixes it.
[Nexus S Android Development] franciscofranco:
I'll revert all the BFS **** and release a test kernel to see if the data drops come from there.
[Nexus S Android Development] phone_user:
Nice! :) in my humble opinion
[Nexus S Android Development] franciscofranco:
Ok update is up. No more BFS code, from this point this will be a CFS only kernel. If you want BFS compile it yourself. I want stability over speed, and this **** is fast enough.
[Nexus S Android Development] got2best:
Sorry for thus question... but ics doesn't slow down after a little while? And what build are u using?
[Nexus S Android Development] polobunny:
*high five*

Don't care for BFS. The gains are marginal, if any, in all the situations I tested.
[Nexus S Android Development] ro_explorer:
Downloaded and installed ... I'll enable deep_idle on this one.

I'll report back in a couple of days :).
[Nexus S Android Development] phone_user:
Thread title still BFS/CFS ;)
[Nexus S Android Development] encinocr:
I never had problems with BFS-Kernel
[Nexus S Android Development] Ibn Saeed:
Wise decision.

It will spare you the headache of handling BFS issues, and let you concentrate on CFS only.
[Nexus S Android Development] qtwrk:
why you guys don't like BFS ?

i have been using BFS version ever since it is released and have encountered no problem ...
[Nexus S Android Development] some_random:
Yeah but we were trying to see if the data problems were deep idle related or just specific to this rom so been using glados for 3 days now not a single data drop with deep idle ON means could be kernel related
[Nexus S Android Development] XxSilent22xX:
I got tired of the weird signal problem I was having while using oxygen 2.3.2 + Franco 16/17 (no issues with 13) even tried with deep idle off, no luck. I switched to cm nightly 259 + 17 and now everything is running great 36+ hours awesome!

Sent from my Nexus S
[Nexus S Android Development] some_random:
What signal problem was that?
[Nexus S Android Development] XxSilent22xX:
Data would stop working while browsing web or tapatalk etc, even though it said connected to 3g and Google servers (green) a reboot would fix it or in some cases fix itself only got a radio dump once but all seems well now that I changed roms.

Sent from my Nexus S
[Nexus S Android Development] nathanson666:
Does that mean that you suspect the data loss issue is related to an issue with the BFS? Would this explain any data loss that happened to people running the CFS kernel?
[Nexus S Android Development] franciscofranco:
Yes it could because to patch bfs there are some other files that need changes that are shared between cfs and bfs builds. The future will tell.
[Nexus S Android Development] vis80k:
i remember you wrote before that frankovs kernel before like 24.10 was showing a much better battery life than those released in this month. were you able to get better battery with the later kernels? just curious. and sorry if i missed your report on that. ;)

Another is when i keep switching from one web page to the other for 20 or so minutes, I get about 24 battery drain... it was only yeaterday i noticed this.

Does this look strange?
[Nexus S Android Development] SA-07:
Yoyo Franco,

Tried that and it didn't work :/

Would you mind trying it out for testing purposes?

Ty
[Nexus S Android Development] frenccw:
Reporting back on Glados 1.8 with deep idle enabled, I've had a few disconnections recently but with slightly different symptoms. The connection would drop itself to zero (no mobile data) and then reconnect automatically but with the icons still greyed out. After that point i still could make calls out, and receive push notifications. Didnt require a reboot/airplane mode to solve the problem.

On NS Collabs 1.50, BLN & touchwake on, no live OC, stock voltages and radio.

Going to continue this run for another 24 hours and then switch off deep idle and monitor the connection. Will report back as usual.

Hows it on your side franco? Any disconnections on your new kernel?
[Nexus S Android Development] franciscofranco:
I can't help if I can't reproduce that issue, I NEVER undervolt, I'm always using stock voltages :/

Thanks for the report. I'm not the best tester right now because I'm with ICS + my ICS kernel and deep_idle and BT conjunction is a little broken (rom issue I believe) so I have deep_idle disabled, but no I haven't run with a single data/gsm/wifi loss for a few days already.
[Nexus S Android Development] SA-07:
Sigh... lemme try stock speeds and voltages as well...

Ill get back to you ;D
[Nexus S Android Development] frenccw:
Heh no worries. I'm very close to just reverting to your kernel and just live with deep idle disabled as it seems to be the least problematic and most stable. I'll persevere for another few days.
[Nexus S Android Development] some_random:
Been testing the same way you have as you know for the past couple of days, I'm going across to franco's new kernel now so I shall let you know how it is with deep idle enabled
[Nexus S Android Development] doc_v15:
Hmm..but how come I have never experienced signal problems since the 1st BFS kernel build until now? What could be the "X" factor?
[Nexus S Android Development] ro_explorer:
Deep_idle is a piece of code integrated into a kernel. Kernels are different, so are roms .. therefore, in this case there "was" a problem (apparently was fixed because my phone is acting great since I flashed the latest kernel)

If you'd have kept reading, you'd have discovered that the pre-Nov1st kernels from Franco did not enabled deep idle even if the switch was ON. Because of that bug, those kernels didn't used at all deep_idle code. All the others kernels were acting like the first ones when I disabled the deep idle.

The last kernel (Nov 23) has more fixes in it and is acting great WITH deep_idle enabled.

You are not on STOCK rom :) ...
[Nexus S Android Development] doc_v15:
Aaaaah, thats why..Stock rom doesnt make a good friend with BFS?
[Nexus S Android Development] EdForce1:
Is it still advisable to use a higher mhz step in min freq? I know franco used 400mhz before?
[Nexus S Android Development] SilverEagle:
Deep idle enalbed, no OC, no UV, lazy 400/1000 with max freq ON and i got my first reboot on screen off. No radio dumps just reboot. Ill try disabling deep idle and see... (im on brainmaster's).

Edit: ok, thats weird...sleep of death without deep idle oO
[Nexus S Android Development] ro_explorer:
I had issues with all BFS kernels tested :).

Are you sure you don't have any UV? The behaviour seems to indicate an instability due to low voltages.
[Nexus S Android Development] SilverEagle:
nope, just checked, ill try without the max freq now (with deep idle)
[Nexus S Android Development] some_random:
I know this... but both glados and franco (and other kernels i'm sure) have this piece of code people in this thread were having radio drops where a restart was needed, I was one of them. So both frenccw and I decided to flash glados (with deep idle enabled so its using that code) and see if there was radio issues.. and both frenccw and I came back with the same result... no I had glados 1.8 on their (same deep idle code as francos 17th) but I had no radio drops, thats why to see if it was the problem franco has dropped all code to do with bfs from his kernel, I am now testing 23th deep idle on to see what happens
[Nexus S Android Development] ro_explorer:
I was saying that even the same code is implemented, the "enviroment" where that code is acting is different so it might generate different behaviour.
[Nexus S Android Development] Zorrich:
I too have been having signal loss with deepidle enabled. So after reading the posts and seeing franco's request for us to try glados, I flashed 1.9 last night. I woke up this morning after having my phone on the charger, and no signal. Had to reboot to get it back. So for me, it is not just the Franco kernel, it is indeed deepidle. I had deepidle disabled for 4 days and not a single problem, enable it with the glados kernel and within 8 hours my signal is gone.

My Rom is carbon (based on oxygen 2.3.1), uckf1 radio, on the 9020a.

Will try Franco 23 kernel when I get home from work this evening.

Edit: I'm using stock voltages, and no OC in any form. Also was using lazy gov, and max freq was on. Min 400, max 1000.
[Nexus S Android Development] Heretic Infidel:
And slowly the reason why deep idle was not implemented is becoming clear ^^

Prolly too much hassle for not enough profit.
[Nexus S Android Development] Flying Fox:
But maybe the idea of deep idle was not born ;) . I never had a signal loss. So thanks to the devs here straining their brains for us!
[Nexus S Android Development] 93ae8074:
I'm beginning to think that a couple of weeks ago too, but I'm gonna try a stock ROM to see if the situation gets better.
[Nexus S Android Development] bdpyo:
Ever try the stock recovery images from rom manager? o_O
[Nexus S Android Development] 93ae8074:
Nope, 'cos I've a NANDROID backup.
[Nexus S Android Development] SilverEagle:
no way, rebooting again, disabled deep idle
[Nexus S Android Development] bdpyo:
I never did, was too much ina hurry. Lol

I wouldn't mind trying though, can't find enough info for me to try it though ..
[Nexus S Android Development] 93ae8074:
Google it mate, download a Full ROM and try if you want it. :)
[Nexus S Android Development] mondo107:
Went back to the Nov17 bfs version, all my incoming calls gets dropped automatically on the Nov23 kernel :( I'm on NSCollab 1.0.50 rom.
[Nexus S Android Development] nathanson666:
I've been running the 23 NOV version since it was released and so far so good! No signal dropout like before.

I have seen the data icon disappear for a bit but then it came back. I think that's normal.

The battery life seems really great too!

I'm running NSCollab .60 with deepidle enabled.
[Nexus S Android Development] frenccw:
My Glados 1.8 test ends today. With deep idle enabled for a week i unfortunately could not replicate the common disconnections i was having is franco 17/11 but i was getting SODs related to tasker triggers (a story for another day). So I will be reverting to franco's with deep idle disabled as it gave me zero problems and is rock solid. Good luck to everyone else trying to diagnose the problem :p
[Nexus S Android Development] r5xscn:
On 23 Nov kernel. Data/gsm drops still occured.

Edit: Deep Sleep, BLN, and BatteryLifeExtender Enabled.
[Nexus S Android Development] ro_explorer:
... couple of days later (47 hours to be more exact):

SETUP:

- kernel - nov 23

- STOCK 2.3.6 rom (the original odexed one) with root access and CWM installed.

- no UV - standard voltages

- no OC: liveOC = 100

- governor: conservative (so the screen off freq. is irrelevant, being active only in lazy gov.)

- 100 - 1000 frequency range

- BLN ON

- deep idle - ON

- no task killers

- data on, 3g-auto, wifi used only when high-speed data is required, sync on

No data drop, no BSOD, great battery life .. NO ISSUES whatsoever :) ...

I'll keep this kernel until the ICS for nexus S will be officially released.
[Nexus S Android Development] noobhero:
Hey ro_explorer, which stock odexed rom are u using? I can't seem to find one??
[Nexus S Android Development] phone_user:
vs

decisive and methodical feedback of the faithful user
[Nexus S Android Development] ro_explorer:
I'm using the official, original rom, the one that was updated over the air after I bought my phone. I don't have a source for it but I have nandroid backups :)

As I said some time ago (I think in this very thread) I'm coming from galaxy S where due to the instability of the original roms I was practically pushed to try and test custom roms. After seeing how smooth and stable the nexus s is with the original software, I've switched to it and I just rooted and installed a custom kernel. The setup is so stable and well balanced that I don't feel the need to go for custom roms, especially if the stock is fulfilling 100% my needs (in combination with the purchased software :) ).
[Nexus S Android Development] Zorrich:
Tried 23 November kernel and just lost signal. 3g icon went white, and couldn't load webpage or send text.

Seems with my setup I cannot run deepidle. Not really interested in changing roms, so I'm just going to disable deepidle and wait for ICS.

Cheers.
[Nexus S Android Development] franciscofranco:
Thanks for the feedback.
[Nexus S Android Development] bdpyo:
Keep up the great work!

I'm dying to try a stock ROM with you're latest and greatest. ;)
[Nexus S Android Development] franciscofranco:
Let's spice things up a bit shall we: testing release is up. There's no rush for a next stable release, but I want to hear peoples thoughts on this one.
[Nexus S Android Development] polobunny:
What sort of spices? :D
[Nexus S Android Development] franciscofranco:
Doesn't matter, try it and see the difference ;)
[Nexus S Android Development] Ezekeel:
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . _________

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ./ It’s a trap! \

. . . . . . . . . . . . . . . . _,,,--~~~~~~~~--,_ . . . .\ ._________/

. . . . . . . . . . . . . . ,-‘ : : : :::: :::: :: : : : : :º ‘-, . . \/. . . . . . . . . .

. . . . . . . . . . . . .,-‘ :: : : :::: :::: :::: :::: : : :o : ‘-, . . . . . . . . . .

. . . . . . . . . . . ,-‘ :: ::: :: : : :: :::: :::: :: : : : : :O ‘-, . . . . . . . . .

. . . . . . . . . .,-‘ : :: :: :: :: :: : : : : : , : : :º :::: :::: ::’; . . . . . . . .

. . . . . . . . .,-‘ / / : :: :: :: :: : : :::: :::-, ;; ;; ;; ;; ;; ;; ;\ . . . . . . . .

. . . . . . . . /,-‘,’ :: : : : : : : : : :: :: :: : ‘-, ;; ;; ;; ;; ;; ;;| . . . . . . .

. . . . . . . /,’,-‘ :: :: :: :: :: :: :: : ::_,-~~,_’-, ;; ;; ;; ;; | . . . . . . .

. . . . . _/ :,’ :/ :: :: :: : : :: :: _,-‘/ : ,-‘;’-‘’’’’~-, ;; ;; ;;,’ . . . . . . . .

. . . ,-‘ / : : : : : : ,-‘’’ : : :,--‘’ :|| /,-‘-‘--‘’’__,’’’ \ ;; ;,-‘ . . . . . . . .

. . . \ :/,, : : : _,-‘ --,,_ : : \ :\ ||/ /,-‘-‘x### ::\ \ ;;/ . . . . . . . . . .

. . . . \/ /---‘’’’ : \ #\ : :\ : : \ :\ \| | : (O##º : :/ /-‘’ . . . . . . . . . . .

. . . . /,’____ : :\ ‘-#\ : \, : :\ :\ \ \ : ‘-,___,-‘,-`-,, . . . . . . . . . . .

. . . . ‘ ) : : : :’’’’--,,--,,,,,,¯ \ \ :: ::--,,_’’-,,’’’¯ :’- :’-, . . . . . . . . .

. . . . .) : : : : : : ,, : ‘’’’~~~~’ \ :: :: :: :’’’’’¯ :: ,-‘ :,/\ . . . . . . . . .

. . . . .\,/ /|\\| | :/ / : : : : : : : ,’-, :: :: :: :: ::,--‘’ :,-‘ \ \ . . . . . . . .

. . . . .\\’|\\ \|/ ‘/ / :: :_--,, : , | )’; :: :: :: :,-‘’ : ,-‘ : : :\ \, . . . . . . .

. . . ./¯ :| \ |\ : |/\ :: ::----, :\/ :|/ :: :: ,-‘’ : :,-‘ : : : : : : ‘’-,,_ . . . .

. . ..| : : :/ ‘’-(, :: :: :: ‘’’’’~,,,,,’’ :: ,-‘’ : :,-‘ : : : : : : : : :,-‘’’\\ . . . .

. ,-‘ : : : | : : ‘’) : : :¯’’’’~-,: : ,--‘’’ : :,-‘’ : : : : : : : : : ,-‘ :¯’’’’’-,_ .

./ : : : : :’-, :: | :: :: :: _,,-‘’’’¯ : ,--‘’ : : : : : : : : : : : / : : : : : : :’’-,

/ : : : : : -, :¯’’’’’’’’’’’¯ : : _,,-~’’ : : : : : : : : : : : : : :| : : : : : : : : :

: : : : : : :¯’’~~~~~~’’’ : : : : : : : : : : : : : : : : : : | : : : : : : : : :
[Nexus S Android Development] RaNd.gr:
Is it possible to have "Advanced routing" (CONFIG_IP_ADVANCED_ROUTER=y) in the kernel ??

VPNC Widget is complaining and my VPN drops very often...
[Nexus S Android Development] doc_v15:
Been using the 23 mov version for 2 days..

So far so good.

Live oc 100

Smartassv2

Default stock

Deep idle enabled

MIUI KelmsMLKing 2.62

Quadrants score 3600 something

Thanks franco!!

Seems like you just CANT STOP GETTING BETTER! :-D
[Nexus S Android Development] Flying Fox:
Have you heard my wishes? I had never dared to ask.... Thx for this (test)-update. That´s exactly what I wanted :)
[Nexus S Android Development] franciscofranco:
Sure, I don't see why not. Will do in a next update.
[Nexus S Android Development] phone_user:
Thanks for test release. :)

＊Added OC frequency states 1.2GHz

(default arm_volt 1200mhz: 1350 mV / int_volt 1200mhz: 1150 mV)
[Nexus S Android Development] franciscofranco:
That's one of the things I changed, yes ;)
[Nexus S Android Development] phone_user:
Users willl give feedback on the other things you changed without prejudice. Because they are cloaked in a shroud of secrecy. So Ezekeel said "It’s a trap!" :p
[Nexus S Android Development] noobhero:
thanks mate, can't remember where i placed my stock nandroid so am trying to search for one untouched, best i could find is one with arabic fix :)

am running on stock for the past few days too, one thing i really miss is controls in notification pull down from CM.

am probably gonna pass the nexus s to my dad soon tho,

- - - - - - -

one report, ran full stock setting for over 2 days then flashed 23rd's kernel over it. ran fine for a few hours. but woke up to an eratic screen everything was mess up, able to wake and lock screen just can't figured what is being display

live oc 105

min 420

max 1050

stock voltage (note that same settings ran without problem on oxygen for close to a week)

deep idle on
[Nexus S Android Development] suksit:
Tried the 25 NOV TESTING build -- I think there are some changes to the Voodoo Color parameters too. Now I get a brief period of green screen every time I turn on the display.

--------

OK. I only get the green screen when on the lowest toggle brightness setting or when using auto brightness. If the brightness is fixed at around 40% or above, the green screen disappears.
[Nexus S Android Development] ShadowVlican:
so far so good with this combination:

ROM: Oxygen v2.3.1 [09/10/2011]

KERNEL: franco.Kernel 23 NOV

NSTools: stock CPU settings, stock voltages, stock stock stock.... except BLN off

battery life is great... network connection holds...
[Nexus S Android Development] krex:
This is because too low color values. Install Voodoo Control and increase RGB multipliers (should be higher than 9xx...) or gamma values (should be higher than -48) at the lowest brightness until the green curtain disappear.
[Nexus S Android Development] suksit:
Yeah I know, just posted because I think the kernel should have the appropriate values by default :)
[Nexus S Android Development] krex:
Ok.

IMHO hard to find "appropriate" value for this. Every display is different a bit and tolerates different values. We should help franco (if I know well he has LCD) what could be the lowest values if we want him to modify the colors for best hue and best battery.
[Nexus S Android Development] Flying Fox:
There is one thing I´d like to know: this is the only kernel (including the former releases) where my settings - UV - keep my device stable. With GlaDOS, for instance, I´m getting many bootloops under my voltage- settings. I know, UV is not so important and actually I don´t need UV. I just want to understand:

i9023

200/1200 lazy

BLN on

Deep Idle disabled

maxfreq disabed

arm volt: 1350/1225/1125/900/875/875

int volt: stock

So my UV between 200MHz and 800MHz is pretty much but hasn´t caused any issue within the last few days/weeks (?) - completely different to my experiences with other kernels!
[Nexus S Android Development] al_madd:
Is anyone here know how to to get rid vbus_present..

Kill my battery..

Use betterbatterystats and under kernel wakelock