yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] invd:
Testing on i9023 with brainmasters miui. No issues so far (not even BLN - works with all 4 buttons), unbelievable fast.

Just one thing ... I really would love to see a CFS version bc in the past it seemed to run more stable on my device...
[Nexus S Android Development] Ezekeel:
Thanks for your feedback.

Yeah, it seems the function that is supposed to disable the touchkeys once the notification is over was not properly called.

After I get another confirmation that BLN is now working properly I will release this fix as GLaDOS V1.8 which will also include the increased display frequency necessary to achieve 65fps.
[Nexus S Android Development] endursa:
i also have no problems with Bln and the test kernel anymore!

Sent from my Google Nexus S
[Nexus S Android Development] Ezekeel:
Damn. That confirmation came faster than expected.

I guess I need some distraction now until I have the kernels ready. Look! A two-headed monkey.
[Nexus S Android Development] JmPTaz09:
1.8 BFS seems really nice so far, lazy at 1ghz/400 deep idle on max screen off on w/CM7 n.259
[Nexus S Android Development] some_random:
good to know that I'm not the only one stumped by this... I was actually running your kernel at the time this happened :\

I know so lazy of me I shall write it up

Rom - cm nightly 257

Kernel - franco's 17th (so not actually sure why I posted this problem here but in my defense it was at like 2 in the morning so I probably didn't know what I was doing :P)

Radio - KF1 (which I only just flashed because I thought it might address that data drop issues.... it did not)

Deep idle - enabled

live oc - 100

UV - yes

sync - google contacts, gmail, calendar and facebook contacts for contacts pics

running apps - settings, gtabsimiclock, facebook, google services, smart keyboard pro (have been running this setup for ages had no problems before)

I have flashed back to my kb3 radio now which I have found personally for me I get the best reception on in my area and am going to do a clean install and then try again.
[Nexus S Android Development] Ezekeel:
Since you already posted it here, try and see if the problem also happens with GLaDOS. If it works fine, this will show that the cause is probably not DEEP IDLE and Franco can instead focus on the differences between the two kernels.
[Nexus S Android Development] some_random:
dude... get out of my head... seriously...

was going to clean install and run your kernel to test just that haha :P
[Nexus S Android Development] franciscofranco:
Exactly! I've been telling people to do that, that would rule out problems with deep_idle, but I already seen reports in this thread from people that use Glados that too had data/gsm loss.

I've fixed it disabling deep_idle (I don't need it that much, thanks to NStools it's an easy toggle option), but to be more precise this were my setups when that loss occured:

ROM: Oxygen 2.3.2 android 2.3.7

Kernel: my kernel 17th november

Baseband: KD1

Phone model: i9023

Options: deep_idle on, liveoc 110%, screenmax_frequency on, bln, stock voltages

ROM: Devnull android 2.3.5

Kernel: my kernel 17th november

Baseband: KF1

Phone model: i9023

Options: deep_idle on, liveoc 110%, screenmax_frequency on, bln, stock voltages

Disabling deep_idle fixed it for me.
[Nexus S Android Development] got2best:
Does disabling live oc fix it?

Because I have the same setup except I am running nscolleb .60 and no live oc, kf1 radio
[Nexus S Android Development] phone_user:
New Version, I'm flashing :) Thanks!
[Nexus S Android Development] some_random:
ok so I have done a full wipe now running cm nightly 259 with glados and kd1

haven't touched any settings voltages are stock live oc 100, deep idle on, bln on. Now I will see what happens and if I get data drop.

also just a quick question, if I set battery life extender charging limit to 100 so that the battery displays that but it always goes back to 96 as soon as I close nstools? any idea why?
[Nexus S Android Development] mike216:
Very quick ezekeel and data signal seems very good also! That's a big one for me. Colors look great also, thanks :-)
[Nexus S Android Development] mike216:
I don't think get has the 100% cosmetic tweak
[Nexus S Android Development] some_random:
yeah it doesn't... just asked that before as well I can't even change when I try to change battery extender in nstools :(
[Nexus S Android Development] polobunny:
Thanks for the 72hz. :-)

What next hmmm...being able to liveoc only for certain programs (games) by making a tasker compatible plugin? I'd love to give my phone the extra boost of 110% only when needed and keep the great battery of stock frequency and a good undervolt haha. Don't like the way NStools is designed and I'm too lazy (get the pun?) to use the terminal all the time. :-P
[Nexus S Android Development] krasnoff:
Not a problem, but it is interesting: when I adjust value LiveOC on 105 or 110, value MinFreq accepts 1050 or 1100 Hz. I change them back manualy on 105 or 110 Hz, but after reboot they are again equal to value MaxFreq. With LiveOc equal 100 everything is all right.

nightly #259, GLaDOS 1.8 BFS, last version NSTools 1.6
[Nexus S Android Development] FloHimself:
I wonder if bet this has bad influence to power consumption e.g. higher drain on screen on!?
[Nexus S Android Development] endursa:
this is my joke :D, if it where a three-headed one ;)

but thx for the kernel update!

Sent from my Google Nexus S
[Nexus S Android Development] 93ae8074:
Yeah, it happens to me too, I think it's related to NSTools.

Cheers.
[Nexus S Android Development] caliban2:
Not getting any data-drops with 1.7 & 1.8

Good news (for me) is that 1.8 didn't break anything from 1.7 (drain). Guess the fps-change will only show in a benchmark, glados always gave me a very fast sys. :)

What i am experiencing with both of them when switching from 3g to wifi and vice versa, is that it can take up to a minute until i have a working data-connection again. Other times the switch is almost instant. It's about 50:50.

I'm trying to figure out if it depends on reception, but is anybody getting the same?

Lazy, didle on, max-freq on, all voltages -25, read my sig.
[Nexus S Android Development] uansari1:
Franco's kernel does the same thing with liveoc enabled. Testing Matrix now.

Edit: Can't even test Matrix, because even when I raise the voltages to Franco's levels, liveoc causes instability leading to freezing and restarts within 20 seconds of boot. I'm pretty disappointed with Matrix at the moment, as I can't get decent battery life out of it even leaving MK's voltages untouched without liveoc or deep idle. Guess I'll wait for an update to Franco's kernel or NSTools, whatever the problem is...
[Nexus S Android Development] SA-07:
Sorry dude.
[Nexus S Android Development] arifhn:
The min-max frequencies both set to max after reboot is caused by nstools. I will update it tommorow.
[Nexus S Android Development] jorim.tielemans:
Is this kernel working with the ICS-rom from Kwiboo?
[Nexus S Android Development] AndiTails:
He released a ICS kernel alpha here:

http://xdaforums.com/showthread.php?t=1355980

But some reported CPU issues so far (seems locked to 1000Mhz) so I'd wait for v1.1 :)
[Nexus S Android Development] polobunny:
That's a good question. I guess it does have an influence, since the FPS isn't capped at 56fps but at 65fps, but I'm not sure if when capped at 56fps it still computes the frames but dismisses them or it doesn't compute them (leaning toward not computing them).

And well, technically, it should drain more too since you're refreshing the panel more often. That's likely minimal compared to games/UI drawing more frames if they aren't capped though.
[Nexus S Android Development] FloHimself:
I tried to proof this with some paper, but sources are hard to find by googling this topic. But it feels natural to me, that a higher refresh rate == more work a second. I guess the display power consumption is directly related to the frame rate, so it is not minimal, but a +10% increase!
[Nexus S Android Development] raulillo88:
I'm having se eral reboots. Now I've connect data mobile and the phone has freezes and reboot. Usually fails when i've just disconnect the phone from AC

Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] mike216:
Damn ezekeel walked my dogs around the block (20 min) while listening to music with deepidle on and liveoc on glados 1.8 and there were two new improvements one is I can liveoc 110 on stock volts with this kernel on nscollab 60 and I didn't loose a single percentage during that time. I flashed before I went for the walk to test the kernel so I don't know if stats are not accurate or if deepidle is just that good in any case thanks alot!
[Nexus S Android Development] phone_user:
satisfied with v1.8 thanks :)

How about additional overclock frequency of 1.2 Ghz when more power is needed? [LiveOC 110 ☞ 1.32 GHz / 220 bus] In my experience on SG kernel, so good. To +10% over bus stable enough even on the frequency of the exceeding 1 GHz. But more % over bus on that, I cannot ensure
[Nexus S Android Development] polobunny:
That's a 10% increase on the refresh though, there's much more to the display than it's refresh rate. What is really killing the battery is the backlight. :)
[Nexus S Android Development] FloHimself:
Sure, that's what I mean.
[Nexus S Android Development] polobunny:
Misunderstood you then. I doubt the impact is really noticeable for the refresh rate alone, I'm more worried about uncapped applications.
[Nexus S Android Development] FloHimself:
Maybe it is just to hard to express myself clearly as a non native english speaker. :/ Anyway, I guess you're right and it's not even noticeable ... :)
[Nexus S Android Development] polobunny:
Don't worry your english is fine, like I said I'm more worried about applications using an infinite number of frames, not capped at X fps than the panel refreshing itself more often. The added draw on that is likely not very big, although I am simply assuming this from my computer background and not bringing facts for this specific device.
[Nexus S Android Development] shubu000:
yeah personally i prefer the kernel without the new increase in fps,

things look like it's tearing, whereas before things were a little slower but quite smooth....

be good if we can switch it back.

is it easy to change the code so that the refresh rate changes back to the previous one? Ezekeel?
[Nexus S Android Development] matmat07:
Just to let you know, I disabled only 3G this night. 16h later (part of the day too :P), only 17% usage. Lot better. Guess i'll activate it manually when I'll need it.
[Nexus S Android Development] polobunny:
I think it's a matter of preference though. Tearing = not in sync. Is it an application in particular?
[Nexus S Android Development] shubu000:
Mostly games to be honest

Asphalt is OK now that I'm more used to it by yeah motion is more smooth with sync

I also find that fruit ninja takes longer to warm up with tyre new refresh rate. But overall the experience is better than on franco'a implementation

Oh 3d app draw as well, although I do like the increased speed of the ui. I'll adjust :)
[Nexus S Android Development] Ezekeel:
I am thinking about that atm.

Good to know we have located the problem. I also have 3G disabled and enable it when needed; also I use the Opera Mini browser which runs fine on Edge.

Currently there is no way to disable it without recompiling the kernel. If more people complain about it I might think about a way to change the frequency on-the-fly.
[Nexus S Android Development] polobunny:
Sounds like a new project... :P

So the 65fps hack, is it really changing the refresh rate of the panel or simply "spoofing" it as a panel that refreshes faster (or uncapping somehow)?

Because if it's the later, it's no wonder it's causing tearing, the frames aren't synced with the refreshes of the panel. Just wondering.
[Nexus S Android Development] IT4ALii3EN:
Thanks for the kernel 1.8!

Perfectly!

I don't have bug, it's the paradise :P

May be, can you dev your own kernels based on crespo:2.3.7 .
[Nexus S Android Development] mike216:
+1 on that 1200 mghz ezekeel! Added on to 1.8 because its blazing fast and perfect
[Nexus S Android Development] aic719:
Ezekeel I hate your kernel! I've been trying to dry the battery for like forever! I can't frickin calibrate my battery! Obviously I'm just kidding hats off dude.. It's been 28 hrs of reasonably high usage and I still have 5%
[Nexus S Android Development] phone_user:
Thanks for your work :)
[Nexus S Android Development] frenccw:
What is the stock min/max CPU freq of the kernel? I've adjusted mine to 400/1000 when using franco's kernel and after flashing Glados it remained the same. So just wondering so i can revert to the stock if necessary. Sorry for noobish post :confused:
[Nexus S Android Development] polobunny:
100/1000 it is.
[Nexus S Android Development] Ezekeel:
Ask morfic for details.

Test kernel with 1.2GHz and 1.4GHz: http://www.multiupload.com/GRXOCHZ117

Untested because I am currently testing ICS.
[Nexus S Android Development] phone_user:
Thanks but can't boot, fix please
[Nexus S Android Development] polobunny:
Boots at 1.2 and 1.4 respectively or safe boot at 1? I'll ask morfic for the rest haha
[Nexus S Android Development] some_random:
running glados 1.8 deep idle enabled

live oc 100

bln on

uv to trinity levels except for 880mhz which has been upped by 50 because its 1000mhz with francos

cm nightly 259

radio kb3

not one single data or network drop my 3g icon hasn't even gone gray once had data the entire time

battery has been amazing here at work now with airplane mode on (don't get reception at work) I haven't dropped a single % which never happens great kernel
[Nexus S Android Development] mike216:
Excited to try the test version but it gets stuck at the Google logo boot screen and kinda fades out the colors. I reset nstools and tried 2 times with no luck,
[Nexus S Android Development] mike216:
Guess your off to bed,can't wait to try that 1200 mghz set! It will be perfect because of the huge gain in speed while still keeping a good undervolt, I hope its just like 1.8 with only the added bump, thanks ezekeel will be patiently waiting, good night :-)
[Nexus S Android Development] mike216:
I think you meant liveoc to 110 ,wouldn't you have to in order to run at 880 mghz, couldn't agree more! Everything seems to be very good. I'm at 1000 lazy screen off Max out 200-1000 25 UV across the board, could go two days if I wanted too,think its time to start using blx to save my battery. That's what the mods there for thanks to our one of a kind dev!
[Nexus S Android Development] Corra:
+1
[Nexus S Android Development] MSgtSimon:
My first SOD on 1.8. Got it to hot boot by mashing on the power button. First real issue that wasn't directly my fault since I flashed 1.8. Flashed a couple radios my phone really didn't like. Oops.

didle enabled

liveoc 110

110/1100 ondemand

arm volt

975

975

1050

1200

1250

int volt stock
[Nexus S Android Development] polobunny:
Try 1275 instead of the stock 1250mv. And crosses your fingers. That's what seemed to kill my phone, the rest I could even run them a bit lower. :)
[Nexus S Android Development] MSgtSimon:
Yea, I've been bumping the voltages for 100mhz and 200mhz up from the 905mv the kernel boots with. 975mv seems to be where my phone likes it. Haven't messed with the middle ones at all.
[Nexus S Android Development] Yusei:
1.8, just perfect.

No signal loss, when using data it's very stable, 2% of drain battery this night with alarm set by alarm Droid.

Until a ICS 100% functional I'll use oxygen with glados.
[Nexus S Android Development] Ezekeel:
Ok. That test kernel is probably broken.

I look into it this evening. Currently visiting some boring friends of my gf and I was not allowed to bring my laptop.
[Nexus S Android Development] mike216:
LOL... I hear you! So act interested so she doesn't give you any problems when you want to fire it up later

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
Keep in mind you guys when under or over volting that you can only take 25 step increments

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] polobunny:
AFAIK NStools enable you to go in smaller increments, unlike SetCPU. Do not know if they are actually applied or it's just aesthetics.
[Nexus S Android Development] mike216:
Morfic says 25 incriments is only possible?

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] polobunny:
That's not impossible, I don't know if he meant with his kernel, with liveOC, with SetCPU and so on. He knows much more than I do about the architecture, I was just mentioning that I thought you were talking about SetCPU vs manually settings liveOC or NStools. ;)
[Nexus S Android Development] mike216:
Well hopefully ezekeel could tell us what's available on this great kernel!

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] waterface:
Tested 1.8 for two full days now, Oxygen KANG by red_skittles, deep idle enabled, min/max 100/1000 lazy noop scheduler, screenoff maxfreq enabled, no OC/UV. Battery has been great, but I got a SoD. What should I try to operate on to see if it happens again?
[Nexus S Android Development] polobunny:
Deep idle disabled. Try and see. If that doesn't work, then try with maxfrequency_screenoff disabled.
[Nexus S Android Development] uansari1:
What's the benefit of noop over deadline?
[Nexus S Android Development] 93ae8074:
I think the question is what's the benefit of deadline over noop.

http://bit.ly/t9myP2

Cheers.
[Nexus S Android Development] Ezekeel:
The voltage changes in steps of 25mV. This is a hardware limitation. You can set the values in between with Custom Voltage etc., but it will actually round up to the next 25mV step internally.

If you have such serious problems as SoD, always test it without OC/UV and with a stable ROM.

I also know that there is a problem on CM7.1 stable which causes the entire UI to crash. The symptoms are pretty much like an SoD except that one can still login with adb shell. The dmsg log reported some binder errors and problem with alarms and logcat told me something about the CPU being pegged. I had this problem also while connected to USB so this is probably not caused by DEEP IDLE. I googled for the errors and all signs point to a problem with the ROM.
[Nexus S Android Development] polobunny:
Ah perfect. Cheers, good to know. :)

Curiosity, how was this found anyway?
[Nexus S Android Development] frenccw:
My charging limited for BLX keeps resetting to 96 in nstools when trying to set to 100. Will be posting in arifhn's thread as well in case it's not the kernel. Sorry if this has been asked before stupid phone app has no search function and computer is down.

Edit: Searched the forum at work and got my answer please ignore this post since i can't delete it -__-'
[Nexus S Android Development] waterface:
Good to hear the master's voice.

What ROM are you on ezekeel? As I said I am on Oxygen 2.3.1 which seems to be considered very stable.

Also, isn't screenoff_maxfreq only a tweak for making deep idle more effective, so to speak? It shouldn't interfere with the stability, right? This is to respond to the other user who suggested disabling it to check if system would be more stable.
[Nexus S Android Development] some_random:
I would like to know the answer..... did a quick search can't find it :confused:
[Nexus S Android Development] jeffkhlam:
me too, please let us know the answer.
[Nexus S Android Development] frenccw:
Earlier in the thread Ezekeel mentioned that he will never implement the cosmetic 100% charging "fix" in the Glados kernel. If you don't already know, the Nexus S only charges to around 96% max to preserve battery life so the limit in the kernel is set just to reflect that.

I don't know if you guys felt the same way, but my mistake was thinking that the point of BLX was to increase the limit to 100 or more(facepalm). In actual fact, BLX is supposed to allow you to decrease the limit as to not charge the battery too high frequently - which consequently decreases battery life. The battery life in BLX refers to the long term life of your battery and not your daily charges. Hope this helps and Ezekeel or anyone else can correct me if i'm wrong :p
[Nexus S Android Development] Ezekeel:
Fixed it. I tested it and it seems to run fine now. Have fun with melting your device. ;)

Test kernel V2: http://www.multiupload.com/1JB4V8O3V3
[Nexus S Android Development] saranyan:
Can you post the CM logs here,

http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority

Might help the CM team to resolve the stability issues with the Nexus s.
[Nexus S Android Development] vis80k:
My phone doesn't like glados.

Battery with wifi on overnight was pretty bad. deep idle was off and on conservative governor gave me 19 percent drain over 7 hours. Maybe this is because battery did not adjust to glados yet.

Another problem is wifi dropping connection for no reason. just now 3g connection also dropped while 3g icon on staus bar was still there. tried to enter airplane mode in this state but nothing happens. trying to enter airplane mode again with long press power button had airplane mode menu greyed out...

Running oxygen2.3.2, no oc, live oc 100, deep idle off. came from franco 17th.
[Nexus S Android Development] phone_user:
Thanks :) Works fine! LiveOC 110, max freq 1.2 GHz (☞ 1.32 GHz / bus 220 MHz). But max freq 1.4 GHz, even Live OC 100 my device rebooted at viewing movie.

I will melt my phone with 1.32 GHz! :)

This test version information of the voltages
[Nexus S Android Development] mike216:
Flys at 1200 and I love it because I can UV by 25 across the board! So far at least,thanks ezekeel feels very fast

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] Ezekeel:
I had similar issues with the data connection when using BFS. Since I switched to CFS the problems are gone.

I think the most efficient way to OC is to maximize the bus/GPU speed. Especially with ICS and its HW-acceleration this will be a huge boost. However I noticed that the lower frequency states like 800MHz seem to tolerate higher bus speeds than the higher states like 1200MHz. I think I will try to start with 1.0GHz and see if I can get an OC value of 120 or 125 to run stable.
[Nexus S Android Development] phone_user:
bfs, mainly on CM-based roms, I have experienced too

Indeed, at 800MHz to +20% LiveOC is stable enough without rasing int_volts :)

echo "1450 1350 1250 1200 1025 925 925" > /sys/class/misc/customvoltage/arm_volt

echo "1250 1150 1100 1100 1100 1100 1000" > /sys/class/misc/customvoltage/int_volt

echo "800000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "120" > /sys/class/misc/liveoc/oc_value

But when more cpu freq needed, at 1.2GHz LiveOC 105~110 useful :)
[Nexus S Android Development] mike216:
Got ya so I'm better off running at lets say liveoc at 105,1050 rather than liveoc 100 at 1200

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] Ezekeel:
I just tried an OC value of 120 with 1000->1200 max frequency and the ICS UI is so snappy, it always makes me jump a little when I close the app drawer and the icons start flying into my face. This is sooo amazing, I feel like am using a different phone. And this prerelease is far from being optimized. :)
[Nexus S Android Development] phone_user:
Cool~~~ :) May I ask your voltages? (arm and int)

Edit : I found the adequate values for my device (max freq 1000, LiveOC 120)

arm 1450 1350 1350 1200 1050 925 925

int 1250 1150 1150 1125 1100 1100 1000
[Nexus S Android Development] mike216:
Ezekeel what ICS build are you running. I want to try a stable version, thanks

On another note this test kernel is crazy with liveoc 105,1260 its insane. And stable so far trying to create a reboot

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] phone_user:
GLaDOS for ICS thread