yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] jordivf:
Clarification:

Talk triggers BLN.

GMail triggers BLN.

Whatsapp triggers BLN.

Messenger (Google plus) doesn't.

Talk about weirdness
[Nexus S Android Development] AeroEchelon:
Almost everything appears to be working, currently my setup is:

Lazy Govenor (210 MHz to 1050 MHz) with 105% LiveOC, UV -25 mV for all frequencies.

I cannot get deep_idle to work: both TOP=ON AND TOP=OFF report as zero. Currently, I've not uninstalled but disabled Google Talk through manage apps. And I've wrote a script to kill bluetooth:

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

However, non of that seems to work. I find it odd that I can't even get TOP =ON to work. Any ideas?
[Nexus S Android Development] technogravy:
Can't seem to extend the battery to 100% it tops of at 96.. Anyone else with the same prob in nstools?
[Nexus S Android Development] mike216:
Ezekiel voodoo is updated could you please make some great colors we desperately need,thanks loving the experience I'm having on your kernel

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] :
Offtopic:

does anybody have the same prob with widgetsoid ?
[Nexus S Android Development] slickrick:
Yeah, but its not a kernel problem, happening for me on stock 4.0.3 with stock kernel as well... Was not like this with ASOP 4.0.X ROMs
[Nexus S Android Development] 93ae8074:
That's exactly is my case, I can add that using a script to change LiveOC percentage don't always changes min. freq.
[Nexus S Android Development] mike216:
Seems people are having lots of minor issues on alpha 15,I'm having none running this beast of a kernel, will have voodoo sound and color soon as supercurio just updated to 4.0.3 and with dsp it sounds incredible, liveOC 110,LAZY

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] fabulous69:
was running very well

wiped cache and dalvik to clean a bit and cant boot properly, the phone bootloop each time....bootanimation, coming to pin, reboot, bootanimation, pin,reboot..

argh!
[Nexus S Android Development] aic719:
And we have voodoo B)

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] Ezekeel:
I have released GLaDOS V2.1 including the updated Voodoo Color and Sound.

Also for DEEP IDLE I have disabled the check for BT until the problem with that is fixed in the ROM. Until then you probably need to disabled DEEP IDLE if you want to use BT. There seem to be some problems with DEEP IDLE not properly used, however strangely sometimes it does work fine. I have not recognized any pattern for that behaviour yet, so we need more testing.
[Nexus S Android Development] mike216:
Love it and we love u

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] aic719:
+1

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] mike216:
It looks so good right now ezekeel thanks a lot it really I really appreciate it

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] technogravy:
Yea I'm facing the same problem
[Nexus S Android Development] mike216:
It seems when the screen dimmer comes on rite before the phone goes to sleep it turns green? Weird

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] :
+1 ^^ damn i agree
[Nexus S Android Development] TrueYears:
So, I have a Tmobile version running stock (and rooted) ICS 4.0.3 but I am a bit confused on the BFS/CFS choice. Which one should I flash?
[Nexus S Android Development] tehgeekguy:
This isn't due to this specific kernel. I got the same thing with the "stock" CM9 alpha 16 kernel. May be something with voodoo?

Try both! See which one fits better for you.
[Nexus S Android Development] uansari1:
CFS is typically more stable.
[Nexus S Android Development] d_phekt:
Same here. Its always been a common issuue with Voodoo Color. Hopefully it will get a fix because I really love Voodoo Color. The green screen is enough to make me nandroid back.
[Nexus S Android Development] maxone001:
Just change the Gamma to alt setting and it will be ok.
[Nexus S Android Development] d_phekt:
Yeah but then it looks like someone pissed in my phone.
[Nexus S Android Development] mike216:
Yep it worked changing to alt,thanks I certainly appreciate the help

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
I'm not getting the yellow changing to alt try rebooting and playing with the other color settings

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] fabulous69:
what is this change, "alt" ? ^^

i missed something, could you explain (any soft to use..?)

thx!
[Nexus S Android Development] maxone001:
Change the RGB setting and add some blue.

---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------

Yes, you need the Voodoo control app on the market. It will enable voodoo sound and voodoo color to work and to let you configure the settings.

---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------

Let's say it's good to have voodoo again!
[Nexus S Android Development] onasri15:
Anyone test this with nexus beam 4.1?
[Nexus S Android Development] maxone001:
Yes and it works fast and with no problem
[Nexus S Android Development] mkoch820:
Soo, I installed it successfully, but this is my first kernel change. How do i get those tweaks? (voodoo colors for example) Do i only have to install nstools, or something else is needed?
[Nexus S Android Development] onasri15:
BFS or CFS with nexus beam 4.1? What's the difference?
[Nexus S Android Development] uansari1:
I'd go with CFS. Difference... CFS = fast & stable, BFS = faster, less stable (generally speaking).
[Nexus S Android Development] onasri15:
What's the risk with BFS? FC's, reboots, or what?
[Nexus S Android Development] uansari1:
I can't tell you for sure, as I never ran a BFS kernel long enough to experience any problems. But I distinctly recall people commenting about experiencing reboots and freezes with BFS kernels, and in some cases, the devs suggesting they flash a CFS version instead.

You can always download both...try BFS, and if you experience issues, flash the CFS.
[Nexus S Android Development] 93ae8074:
Deep-Idle not working

Hi there,

I can't get Deep-Idle to work even after freeze Talk and entering and leaving camera app.

I'm on stock 4.0.3 and the kernel is awesome at 110% LiveOC but I miss Deep-Idle kicking in. I hope there is a solution. If you guys know where to look, please let me know.

Cheers.
[Nexus S Android Development] damnmisur:
Voodoo control app from market is needed.

Sent from the bowels of hell
[Nexus S Android Development] ranadroid:
Thanks man your the best flashing 2.1 now.
[Nexus S Android Development] toyface:
Thank you for letting us know there's an app on the market, I've even been to the project voodoo website and there was no mention of an app ha ha.
[Nexus S Android Development] maxone001:
My pleasure.
[Nexus S Android Development] Serious_Beans:
Basically bfs is bursts of speed and less stability, but cfs has constantly same speed and more stable...from what I understand.
[Nexus S Android Development] onasri15:
CFS it is. Deep idle doesn't work?

And also, what are people's quadrant results?
[Nexus S Android Development] mkoch820:
Got it, but I found only sound settings, how do i get the rest of settings?
[Nexus S Android Development] maxone001:
Nstool from the market and voodoo control is the only 2 apps you need to configure the settings.
[Nexus S Android Development] mintcoffee:
Anyone notice BLN isn't working with v2.1 kernel? The keys aren't lighting up for me when I get a notification on ICS 4.0.3.
[Nexus S Android Development] ragnarokx:
BLN is working for me.

But this kernel seems very unstable - got a reboot as soon as it first booted, then a few minutes later the screen was changing colors in a checkerboard sort of way. Perhaps this Voodoo patch doesn't like my phone.
[Nexus S Android Development] d_phekt:
I tried again with yours and other suggestions with no luck. Still getting the green flicker when turning the screen on or off. Also tried messing with the brightness, tried turning automatic brightness on and off. I have always used custom settings in Voodoo Control. Frustrating that I can't even use it with the stock washed out settings. Can someone that has gotten it to work please post their settings?
[Nexus S Android Development] ranadroid:
Hmm.. it working perfect for me plus i UV -50 mV from all freq. Also it seems like score in quadrant increased a bit as well... What rom are u using it with?
[Nexus S Android Development] mintcoffee:
I'm using it with AOSP+ v1.0 from AndroidUser00110001. The ROM has some issues with the latest versions. I'll flash to the stock ICS and try again. Thanks!
[Nexus S Android Development] ranadroid:
You can try NexusBeam 4.1 thats what im using.
[Nexus S Android Development] onasri15:
How much does UV -50mV affect battery life? Also does it affect anything else?
[Nexus S Android Development] jroid:
this kernel has stability issues. I got random reboots during phone calls. 3 random reboots on each of the 3 important phone calls I had..VERY annoying. Flashed back to stock kernel until it's fixed.
[Nexus S Android Development] uansari1:
I'm on NexusBeam, and Voodoo Control reverts back to the stock settings on a reboot. I've tried a couple times, and I can adjust the settings to my liking, but a reboot causes it to revert back.

Any ideas, or anyone else seeing this?
[Nexus S Android Development] ranadroid:
I dont see a BIG difference... but I'm sure it does makes a lil diff. But undervolting can affect stability depending on your phone. Some phones can UV more than others and some are more sensitive to UVing.
[Nexus S Android Development] caliban2:
This kernel (2.1 cfs) is perfect, stability wise. And feels very fast too! Voodoo sound is fine. (Had it working before with 2.0 though by loading the module via voodoo control plus ^^)

Getting a bit of top-off now with 2.1, but very low numbers. What's still there: min=200 mhz, max-freq is greyed out.

Lazy-gov, voltages & freqs unchanged, stock-ics rooted.
[Nexus S Android Development] ranadroid:
It reverts back if u manually reboot phone???
[Nexus S Android Development] onasri15:
I'm getting mixed signals from you guys. Some people say it's unstable with dropped calls and stuff, and then some of you say its amazing.

I wanna clarify some things:

1) How long battery life you guys getting?

2) Is it stable or not? Dropped calls or no?

3) Is deep idle actually working?

4) Is everyone getting the green tint or no?
[Nexus S Android Development] JimmieMaul:
I'm also getting a green flash when locking the phone on a i9020a running NexusBeam 4.0.3
[Nexus S Android Development] albundy2010:
Congrats on winning a GN Esekeel
[Nexus S Android Development] tehgeekguy:
Wooooo! Yeah, congrats Ezekeel! You definitely deserved this win!
[Nexus S Android Development] ragnarokx:
Stock ICS. Flashed back to 2.0 because that was very solid for me.
[Nexus S Android Development] uansari1:
Yes! Shutting down and restarting the phone reverts the settings.

As for the green tint, yes I've noticed that as well. In my experience, it's all about the gamma settings. Personally, if I just reset them back to the 2.3.3 defaults, there's no green tint when I click the power off or on. Colors look fine to me. Problem is that the setting won't stick, and the default kernel setting isn't right.

Yes... that's what I'm about to do as well.
[Nexus S Android Development] ranadroid:
Ur right the color settings did reset after reboot but sound didnt... i guess i will stick with default color for now...other then that its
[Nexus S Android Development] uansari1:
I saw in a post in Mathkid's kernel thread that only Voodoo color needs to be baked into the kernel, whereas to use Voodoo sound, we just need the app from Market. If that's the case, then going back to v2.0 and simply downloading the app would be "best" if anyone's not digging the colors.
[Nexus S Android Development] demo23019:
Use this method to make colors stick

http://xdaforums.com/showthread.php?p=19782699
[Nexus S Android Development] ranadroid:
I had voodoo control installed before but i couldn't edit sound on v2.0 sooo idk...

thanks :)
[Nexus S Android Development] caliban2:
On ics it only worked with the version supercurio released today, about 12 hrs ago. And I see there's another one already.
[Nexus S Android Development] onasri15:
God damn don't install cfs with nexus beam 4.1. 2 reboots in 5 min, charging limit won't go to 100 and deep idle is showing 0 everywhere. Needs a fix.

And is it possible to get the kernel with stock boot animation?
[Nexus S Android Development] tehgeekguy:
1 - I haven't had any reboots in the past couple hours on Beam 4.1.

2 - the 100% thing is purely cosmetic. It just makes it look like it's charging to 100%. I like having a true representation instead of a padded number.

3 - If you don't like the boot animation, remove it from the .zip. It's in /system/media
[Nexus S Android Development] kieronboz:
What apps you guys use for your OC and UV then?
[Nexus S Android Development] tehgeekguy:
You could use NSTools or SetCPU, probably No Frills CPU too, although I haven't used that one myself. Personally I don't UV past any stock UV that's built in the to kernel.
[Nexus S Android Development] kieronboz:
I used setcpu when I was on ginger, so I guess I'll just carry on with that unless you think nstools is better? Thanks :-)
[Nexus S Android Development] terryhau:
Is the default min frequency meant to be 100mhz ?

I can't tell since all CPU freq tools can't set/show below 200mhz on the new kernel.
[Nexus S Android Development] phone_user:
[CONTEST #4] Custom Kernel Creators Can Catch GSM Nexus Fever

Congratulations! The Lord of the kernel MODs:)
[Nexus S Android Development] climhz:
congrats Ezekeel, hope u have enough time for both phones!
[Nexus S Android Development] arifhn:
Do you use NSTools? Its nstools problem, not the kernel

Congratz!!

GLaDos ver 2.0 don't have logcat module, am i right? Anyone can enable logcat?
[Nexus S Android Development] terryhau:
I know that, i was asking what the default min freq is meant to be.

logcat is working.

Hopefully it won't be removed. I need it, and every other kernel out there seems to be removing it. Has anyone benchmarked any differences with it on or off? It's not just useful for developers. When something doesn't work or crashes you can check logcat to see why.
[Nexus S Android Development] arifhn:
ok. just updated my device. I'm working on it
[Nexus S Android Development] cabstrak:
Ezekeel, can you put back up the link to download GladOS v1.12 (or whatever version you were last working on before Kernel sources for 3.0 is out)?

I'm still not liking ICS yet..
[Nexus S Android Development] Evo_Shift:
Oops delete
[Nexus S Android Development] saryu:
whenever i turn my phone to 1.2 ghz, it straight reboot my phone... any idea?
[Nexus S Android Development] demo23019:
Might have to bump voltage idk

I've been running 1.2 with no issues
[Nexus S Android Development] aLNG:
For stock kernel in ics, the default min freq is 200
[Nexus S Android Development] demo23019:
I use no frills CPU to overclock and I have 100mhz option

I have mine set @ 1.2/100 with no problems

Edit

Never mind it runs at 200mhz when I select 100
[Nexus S Android Development] arifhn:
After doing some test, the problem that we can't set cpu freq lower than 200MHz

I've found that the problem is not in nstools

here is nstools debug log

D/NSTools.SysCommand( 1282): echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
D/dalvikvm( 1368): GC_FOR_ALLOC freed 81K, 7% free 10242K/10951K, paused 46ms
D/NSTools.BasePreference( 1282): WOK
D/NSTools.BasePreference( 1282): read from /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
D/NSTools.SysCommand( 1282): cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
D/NSTools.BasePreference( 1282): ROK:200000

to make sure I've modified your kernel to print some debug message

drivers/cpufreq/cpufreq.c line 389

printk(KERN_ERR "------- new_policy.object=%u\n", new_policy.object); \
ret = __cpufreq_set_policy(policy, &new_policy);	\
policy->user_policy.object = policy->object;	\
printk(KERN_ERR "------- policy->object=%u\n", policy->object); \

and dmesg result

<3>[ 131.345768] ------- new_policy.object=100000
<3>[ 131.345856] ------- policy->object=200000

I know, setting the value via terminal always work. But with nstools sometime works, most don't work.

Is there something wrong in the new kernel?
[Nexus S Android Development] LuffyPSP:
Love the 2.1 update! Using stock cpu freq with lazy governor.

Nuked from Samsung Galaxy S2 GT i9100 using XDA Premium app
[Nexus S Android Development] demo23019:
Ur using with a gs2?
[Nexus S Android Development] navillos:
Seriously? dude look at his sig
[Nexus S Android Development] demo23019:
yea galaxy s 2 i9100

And I wwasnt serious lol
[Nexus S Android Development] kevin0905:
i get stuck on the google logo... flashed cfs version on latest bm's gingerbread miui

nvm.. its only for ics

can anyone link me to the 1.12 version?
[Nexus S Android Development] mike216:
This kernel is great but my only issue is a reboot while on a call earlier today,I liveoc at 110 then I went down to 105 and I got another so I went to stock and so far so good! Running alpha 15 ondemand

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] aic719:
Tried pushing the volts up by a bit?

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] FloHimself:
I experienced a reboot while using a BT headset and deep idle. Hmm... rough times for deep idle: CAM bug, BT bug... :(
[Nexus S Android Development] chronikfatigue:
Brainmasters 4.0.3 with Glados 1200 MHz Performnce GPU rendering and processes limited to 4.

One of my best ICS results yet.
[Nexus S Android Development] Ezekeel:
I probably also will remove the logging functions later on when everything is working stable, however I always include it as a module which you can load on boot.

Sorry, I do not archive these.

That is strange. Yeah it looks like a problem with the freq code in the kernel. But why does it only happen from within NSTools and not when changing it manually? I will look into it.

Currently the check for BT is disabled in DEEP IDLE, so it might cause problems. Best is to disable DEEP IDLE when using BT. But yeah, there seem to be alot of problems in the ICS ROM which cause problems with DEEP IDLE. I will see if I can locate the bugs in the ROM and get Google to fix them. Maybe will need help from a capable ROM dev for tracking these bugs down, so I will look into that freq problem first.
[Nexus S Android Development] arifhn:
I think i found another clue.

Can anyone confirm this:

Use nstools, set min freq to 100, but don't click it directly, hold the '100MHz' item +/- 1 second then release.

It will work.
[Nexus S Android Development] Ezekeel:
Hmm. Sounds like the problem is with NSTools then. Maybe the kernel needs some time to set the freq properly and you have to put in some longer delay between writing the value and reading it.
[Nexus S Android Development] 93ae8074:
Confirmed.

Changing matters, I did some trying using command line and I had problems activating 110 LiveOC, sometimes min. freq. keeps at 100 or 200 in place of 110.

Cheers.
[Nexus S Android Development] arifhn:
I've tried to disable read value. (Only write without read) still not work.

Strange...
[Nexus S Android Development] Ezekeel:
Ok. I got a few more observations and a possible explanation for that min freq issue.

Test I:

Set a static wallpaper; set min freq to 100 -> min freq shows 100

Change to a animated wallpaper -> min freq increases automatically to 200

Change back to static wallpaper -> min freq decreases automatically to 100

Test II:

Set a static wallpaper; set min freq to 100 -> min freq shows 100

Open a game (I tried World of Goo) -> min freq increases automatically to 200

Close game -> min freq decreases automatically to 100

I think this behaviour is intended and the reason is the HW acceleration that came with ICS. At a freq of 100 the GPU and bus only run at half speed while at all other frequencies they work at full speed. So I guess Samsung/Google decided that when the HW acceleration is used it should be always used at full speed to get the most out of it.

Note that setting the min freq to 100 while the HW acceleration is used will not automatically change the min freq to 100 once the HW acceleration is not used anymore. So if you want to set the min freq to 100, you must do that while the HW acceleration is not active, for example at boot with an init.d script. That kinda sucks.

EDIT: Yeah I was right. I found it in the kernel source. I will see what happens if one disables this feature.
[Nexus S Android Development] metalgear873:
Wow what a great kernel! This is my first time using it. Simply great.

It is also nice to see what version I'm getting of the mods
[Nexus S Android Development] 93ae8074:
Can possible be deep-idle not working related to an animated wallpaper then?
[Nexus S Android Development] ramon.dexter:
How do I disable the battery life xtender? I want to see my baterry charged to 100%.

I use NStools, change the value to "100%", click "OK". I see that superuser granted nstools su access, but nothing happens. I still get the 96%, set by default. How do I change it?
[Nexus S Android Development] arifhn:
100% battery is not related to BLX.

its different patch, Ezekeel didn't include the patch in his kernel because its only cosmetic change

btw its FAQ, i beleive you can find it if you search

@Ezekeel

another problem is, i can not find this file in the new kernel

/sys/devices/system/cpu/cpu0/cpufreq/lazy/screenoff_maxfreq

should i change it into this /sys/devices/system/cpu/cpufreq/lazy/screenoff_maxfreq ?
[Nexus S Android Development] irminsul:
I have the same issues, I can't change it

Verstuurd van mijn Nexus S met Tapatalk
[Nexus S Android Development] Ezekeel:
Yes, the per-cpu cpufreq interface has been deprecated and is replaced with the global interface at /sys/devices/system/cpu/cpufreq/.

EDIT:

I removed that annoying min freq feature and everything still seems to be working just fine. I have uploaded the kernel, so you can give it a try.

Download: http://www.multiupload.com/Y25ZMXJSJF
[Nexus S Android Development] djjonastybe:
My device crashed after lowering max freq to 800. no custom voltages. NSTools seems to be crashing a lot as well with official ICS.

Still everything is working perfect so far.
[Nexus S Android Development] 93ae8074:
Curiously it helped a lot with NSTools crashes. Modification working fine.
[Nexus S Android Development] damnmisur:
Write a script for it with scripter in rom toolbox. There is a post in the themed and apps section. The setting numbers do not apply anymore. You will have to change those to your preference.
[Nexus S Android Development] michalurban:
Kernel flash

Hi, just two quick questions:

1) Before installation of the new kernel, I should save my EFS folder, right?

2) After installation of the kernel, should I make a complete wipe (data/dalvik/cache) of the phone?

Thanks ... just asking so that I wouldnt copy 10Gb of music twice ... :)
[Nexus S Android Development] bioan:
1. Yes.

2. Wipe only cache before installation.
[Nexus S Android Development] caliban2:
Cache and dalvik-cache, to be precise. But glados does this automatically when flashing, via a script inside the zip. :)
[Nexus S Android Development] nwbee:
why does my samoled screen become yellow when going to sleep?

i'm using glados 2.1 cfs + nexusbeam 4.1
[Nexus S Android Development] onasri15:
Ezekeel can you help me with flashing? I did Cfs and bfs 2.1 and constant reboots whenever I turn my screen off. Same with matrix.

I'm running nexus beam 4.1 now
[Nexus S Android Development] maxone001:
It's the voodoo color, you have to put the Gama setting to Atl.