yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] juliano_q:
I had this problem 2 times with speedy-2, now with speedy-3 it is stable but I noticed that two people had it. No idea of the cause. I am making a fresh nandroid backup everyday to be able to restore if it happens again.
[Nexus S Android Development] stewarta:
ICUP FCs

None on my i9023 ....
[Nexus S Android Development] cpaixao:
Yes. See my early post.
[Nexus S Android Development] neinfricatu:
This kernel rocks.

70% battery with 1h display on, after 15 hours with cm9 alpha 18 rom. Can't get any better. :)
[Nexus S Android Development] kodora:
I´ve had the same bootloop problem on speedy-3 and with AOSP+. Wiped, flashed ROM than speedy-2 and all is ok now! ;)
[Nexus S Android Development] juliano_q:
Guys, please post here the logcat for eugene if you had the FCs + bootloop problem.
[Nexus S Android Development] kodora:
I just didn´t get a logcat because I was away from the pc and had to restore my phone back to working. Otherwise I had do it so that eugene could check why it´s happening. ;)
[Nexus S Android Development] GerManiac:
Using v3 with AOSP+2.1.1 ROM on I9023. Now 17 hrs 18 min and counting, still have 27% battery. Amazing! No reboots, or FCs. WIFI is on all day.

Sent from phone
[Nexus S Android Development] liquelt:
why you juliano_q are making nandroid backups everyday?

just make one and keep it in case of something going wrong.

simple like that... this is what I do.

Just complementing, I have been using the Speedy-3 for 3 days and it's just perfect.

I don't care about quadrant results and I am not actually using overclock.

Anyway, keep your backups. You just don't need to do it everyday.

LOL
[Nexus S Android Development] AeroEchelon:
After using GlaDOS for the past 2 weeks or so it is refreshing to finally have a stable kernel which offers good battery life. I am a true advocate for Ezekeel's work on DEEP IDLE but your implementation seems to be a bit better. I notice less awake time when my phone is in my pocket versus any other kernel.

It's refreshing to finally see uptime > 48 hours. (No random reboot during phone calls as I always experienced with GlaDOS.) Really stable kernel!
[Nexus S Android Development] coloxim:
Sorry for the question..but the minimum frequency is always 200mhz?

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] juliano_q:
I am obviously doing it because I change a lot of things in my phone everyday and if I need a backup I want it updated.
[Nexus S Android Development] maniac2403:
Unless you are using live wallpaper, min freq is 100Mhz.
[Nexus S Android Development] evcz:
Tired of poor official battery performances I just flashed this kernel, let see how it goes :-)
[Nexus S Android Development] suksit:
I'm on Speedy-3 kernel.

Today I was downloading an app from market using mobile data and when the 1-minute screen off timeout is reached, my phone just turned itself off completely -- no reboot or anything. I have a feeling that LiveOC is the culprit.

My setup was as follows:

BLD: ON

BLN: ON

Scheduler: cfq

Governor: smartassV2

Min/Max freq: 100/1000 MHz

LiveOC: 120%

Voltages: default
[Nexus S Android Development] deani77:
Speedy-3 have liveOC?
[Nexus S Android Development] cllangfo:
Freeze

I was surfing on the net today and my phone froze. Could only remove the battery to reboot, however, the phone stayed on the boot up screen. Nandroid backup was the only thing that worked.

Stock with Speedy-3
[Nexus S Android Development] Bob889:
I have tried other kernels and speedy-3 is the most stable, also battery life is awesome. I'm at 2 days 2 hours on current charge with 31% left. running rooted stock 4.0.3.
[Nexus S Android Development] suksit:
Well the option is enabled in NSTools so I guess yes :confused:

--------

Forgot to mention that I compiled it from the code in Eugene's github and the only changes I made was commenting out all Voodoo stuffs. Could that make it unstable? However, I put LiveOC back to 100% and everything seems to be stable until now.
[Nexus S Android Development] maniac2403:
No, Speedy 3 does not have live oc..
[Nexus S Android Development] xjerlzx:
Strictly speaking about battery life, is GLados or This kernel provides a better battery life?
[Nexus S Android Development] xjerlzx:
Can you please share ur settings?
[Nexus S Android Development] _yaz_:
what did u use for settin up ? anyway, i don't think loc add anything to the performance. at least, my experience is just instability w/loc. now i keep up w/eugene recommendation; "keep it as it is". rocks like hell :D
[Nexus S Android Development] AeroEchelon:
I currently use:

BLD ON, 500 ms

BLN ON, Blink Off

smartassV2, 100MHz to 1000MHz

IO Scheduler: CFQ

Default Voltages

... I also use Nova Launcher instead of the stock launcher which is more customizable and more memory optimized. I don't experience as many widget redraws when using the phone.
[Nexus S Android Development] mixtapes08:
which is better deadline or cfq?
[Nexus S Android Development] suksit:
I use NSTools from Market.

Also agreed about LiveOC, I use it but can't really see the difference in performance.
[Nexus S Android Development] coloxim:
I'm not using livewallpaper...

but still 200mhz..

how can set 100 mhz?
[Nexus S Android Development] :
have you tried matrix 14 cfs? fast, stable, and excellent battery:)
[Nexus S Android Development] cpaixao:
The answer is: YES. And i have just one word to express my experience with it:

"Freeze"
[Nexus S Android Development] dsellers2:
Based on my test. I used up to glados version 2.6, Eugene's speedy 3 kernel saves approximately double the battery while sleeping. This kernel feels smoother too, but they drain around the same while the display is on. Hope that helps.
[Nexus S Android Development] dsellers2:
Personally I like deadline. I've never tryed cfq though, but that's because I've never had issues with deadline and this kernel as my default governor.
[Nexus S Android Development] _yaz_:
strange. whenever i start nstools the min freq pops to 200mhz and no way to force back down to 100.

amof, i experience the best performance w/the default settings of this kernel so i'm about to stop all the system hacking tool i used before (on GB).
[Nexus S Android Development] ragnarokx:
I always wondered this: does it really matter if the minimum frequency is 200MHz? They use the same voltage, so shouldn't battery drain be the same for 100MHz and 200MHz?
[Nexus S Android Development] maniac2403:
I did try Matr1x cfs v14. It's a good kernel, but battery life is so much better for me with Speedy-3. 1d 8h + battery is normal for me. With Matr1x, I got an average battery life of 18 hours.
[Nexus S Android Development] _yaz_:
u're probably right. i just asked it because i haven't managed to set min freq to 100 w/NST ever.
[Nexus S Android Development] maniac2403:
Stock kernel comes with 100/1000. If you use NSTools, the min freq goes up to 200Mhz. I use set cpu now to change governors.

Since, voltages are the same for 100 and 200 Mhz, I don't think you would see a major hit on your battery life.
[Nexus S Android Development] evcz:
How is blx set into this kernel by default?

Battery charges up to 96% like in stock kernel?
[Nexus S Android Development] coloxim:
i'm using it...very nice...and i can set 100mhz..
[Nexus S Android Development] maniac2403:
By default, battery charges to 100%
[Nexus S Android Development] Hostile89:
The min freq is linked to hw acceleration as the gpu and bus only run at half speed at 100 and full speed >200. NSTools is not the cause. This post by Ezekeel explains it better.
[Nexus S Android Development] benrees21:
Please add Simple IO Scheduler. Thanks.

Sent from my Nexus S on Ultimate ICS ROM, and some help from Tapatalk!
[Nexus S Android Development] ZeDestructor:
Charges to 96%, but cosmetically reads 100%. Its mentioned on P1 iirc.
[Nexus S Android Development] :
Man, this question sent me into a flashback... and it took me two hours to find where I'd seen this discussed, but here it is:

http://xdaforums.com/showthread.php?p=18150277#post18150277

It's a few pages of reading, but all the top kernel devs weigh in on the matter. Perpare to be schooled!
[Nexus S Android Development] evcz:
Yeah that's what was confusing me. From nstools I'm not able to change che max charging value. I would prefer if it was set to 96 :-P
[Nexus S Android Development] maniac2403:
It does explain it to some extent. But not using NSTools, always makes the 100Mhz stick. This behavior could not be explained by the post.
[Nexus S Android Development] ragnarokx:
So according to that thread, 100MHz and 200MHz cause about the same amount of battery drain.
[Nexus S Android Development] xjerlzx:
For me

Bld off

Bln on

Smartassv2 100-800

Io scheduler cfq

Default voltage

And damn u are right batt life last helll longer! Andriod os bug seened to be fix. 3hrs drop only 2percent with wifi on and andriod os 3% only

Wao!
[Nexus S Android Development] ragnarokx:
Anyone know how to disable BLN blinking without NSTools? I have blinking set to off in BLN Control Pro v0.15.20, but when I do a test notification it still blinks. I tried running this script also:

#!/system/bin/sh

echo 0 > /sys/class/misc/backlightnotification/blink_control

But blinking continues when I do a test notification. :confused:

Edit: nevermind, I found my problem. The script to disable BLN blinking is:

#!/system/bin/sh

echo 0 > /sys/class/misc/backlightnotification/in_kernel_blink
[Nexus S Android Development] rrohanjs:
is it compatible with this rom ?

http://rootzwiki.com/topic/12956-rom-aosp-android-open-kang-project-crespo-build-14/page__st__40
[Nexus S Android Development] JakeOcn:
Yes, it is compatible
[Nexus S Android Development] _yaz_:
aaa, thank you ! i've been looking for this thread, as well. however ...

my typical operation is listening music w/screen off. it takes several hours a day ! i can clearly see the difference if 100mHz is enabled or not. maybe other way of use makes it insignificant but not for me.
[Nexus S Android Development] Hostile89:
By default the min freq can be 200mhz depending on whether hw acceleration is used. SetCpu is capable of changing this to 100mhz. NSTools apparently does not.

I was trying to state that the default min freq had been upped by Google dependent upon the new hw accel requirements and NSTools is not capable of changing this to 100mhz.
[Nexus S Android Development] Bamdroid:
This kernel is ****in amazing.

....carry on.

Screen on time seems a little hungry but overall I liked the results on 1 day of testing..

私のネクサスSから送ら
[Nexus S Android Development] harisn:
Database error from the download site. Any mirrors?
[Nexus S Android Development] suksit:
Eugene asked us not to post direct download links. Please see the first post.
[Nexus S Android Development] ZeDestructor:
Its not implemented here afaik, similar to the different implementation of Deep Idle/Deep Sleep which NSTools fails to see but CPUSpy does.
[Nexus S Android Development] paprkut:
Same here
[Nexus S Android Development] S_Dot:
Website is still down :-/
[Nexus S Android Development] tchaari:
maybe eugene is preparing a new update for us :D
[Nexus S Android Development] S_Dot:
Forum is back online but it's linking to speedy-2?
[Nexus S Android Development] you_eeeeeediot:
Not even that anymore... that website has been blanked back to default apache. :( wish there was a mirror we could use, I'm holding off my install of AOKP until I can grab this kernel.
[Nexus S Android Development] maniac2403:
Here is a google cache of the website which Eugene had linked to. For anyone who needs it, get it from here:

Eugene 3.16 ICUP Speedy 3

Did not post a direct link to the file, because Eugene asked us not to.
[Nexus S Android Development] evcz:
When charged my phone reports 100% while using this kernel :-\

is that real or just cosmetics?
[Nexus S Android Development] maniac2403:
Just a cosmetic change. Battery sill charges to only 96%.
[Nexus S Android Development] _yaz_:
as i see on twitter, eugene is quite busy w/vibrant now. i don't expect new crespo kernel soon ;)
[Nexus S Android Development] evcz:
Great, thank you
[Nexus S Android Development] provolinoo:
Bad news... do we need to move to another kernel? :(
[Nexus S Android Development] melvinchng:
Kernel doesn't have to keep updating as long as it is new.... but Google just released kernel 3.2 for Linux, and it is great for battery saving. I think something is coming soon.
[Nexus S Android Development] S_Dot:
I'm getting some serious touch screen issues with speedy 3 and some random reboots and lock ups.
[Nexus S Android Development] KrisMurdrum:
Well this is strange. But in the last three days, whenever I charged my phone up to full battery it has SOD'd. Then after battery pull and boot I'm down to 70% battery.

OTA ICS

-no tweaks

ICUP S3

-100/1000

-cfq

-stock voltages

Carved into runes with my ICS powered Magic Rune Stone
[Nexus S Android Development] ZeDestructor:
Indeed, as long as it works properly, there isn't much reason to need updates. I'm one of the (seemingly) few people for whom all three versions of Speedy worked perfectly.

Btw, the Linux Kernel is headed by Linux Torvalds, its creator, not Google. Google makes a patchset that's applied onto the mainline Linux kernel, which kernel devs like eugene373 further patch and/or port to newer versions of the mainline kernel.
[Nexus S Android Development] ragnarokx:
Anyone successfully using scripts in the init.d folder? I'm trying to disable BLD. My script works fine when I run it manually, but doesn't work in that folder at boot.

Sent from my Nexus S
[Nexus S Android Development] brainmaster:
It doesn't have anything to do with the kernel, but with the ROM that you're using. If the ROM doesn't have the init.d scripts support, then its failing to load the scripts on the boot.
[Nexus S Android Development] ragnarokx:
Interesting - you would think CM9 would have this. Guess they haven't added it in yet.

Sent from my Nexus S
[Nexus S Android Development] brainmaster:
Do you have already the init.d folder in your ROM zip file? If yes, then probably your scripts have errors.
[Nexus S Android Development] ragnarokx:
Yup, init.d folder is in the ROM zip. This is my script:

#!/system/bin/sh
echo "0" > /sys/class/misc/backlightdimmer/enabled

I currently have ROM Toolbox run this at boot and it works. But when I make a script and place it in init.d it doesn't work.

Sent from my Nexus S
[Nexus S Android Development] Jabaculemos:
I'm getting some weird readings of my battery percentage with this kernel...

Today I checked the battery usage and there was a gap in the graph, over 10% of the battery simply "disappeared".

Then I was down to 7% and plugged the phone in the computer to copy some files, after I rebooted the phone my battery was at 28%! I mean, it was plugged for no more than 10 minutes and the screen was on during most of that time, so clearly there's something wrong!

I have already performed battery calibration twice. Any ideas?
[Nexus S Android Development] brainmaster:
Is your script saved in the UNIX file format? Have you set the permissions to 750 for that script?
[Nexus S Android Development] AeroEchelon:
I've experienced this "problem" ever since I owned an Android phone. It's nothing to worry about really, whenever a reboot occurs (especially random ones) your battery reading will be a bit skewed. That 10% that was missing at the beginning of your day was not in fact missing as your battery reading shown an increase during that second reboot you experienced.
[Nexus S Android Development] ragnarokx:
I just edited and re-saved the script on my computer using TextWranger (Notepad++ equivalent for OSX) to make sure it was in UNIX format. Transferred script back to the init.d folder, set permissions to rwxr-x--, and still no go.

I'm not sure what ROM the kernel is being used on in this thread, but they also have this problem.
[Nexus S Android Development] Jabaculemos:
Thanks for the info!

Weird, the reboot I mentioned in my post was the only one I had today, at least the only one I noticed (maybe my phone rebooted during the night).

I don't remember this happening too much with the stock kernel, that's why I thought it might be a problem with this kernel...
[Nexus S Android Development] suksit:
Actually it does depends on both ROM and kernel (boot image to be exact) -- the ROM needs to have busybox installed and the boot image needs to have a service enabled in its ramdisk init.rc file. The lines to be added are: (credit goes to @nexusphone's post)

service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
class late_start
user root
group root

Normally, this problem is already handled with kouch's AnyKernel, which will use the current ramdisk on the ROM. But in case of Eugene, he uses his own ramdisk in the zip package, which apparently does not have this service enabled. So in order to make init.d work properly in ICUP we have 3 choices:

Edit the ramdisk image in Eugene's zip package, or

Take the zImage and all modules/libs in the zip and put them in the original AnyKernel package, or

Ask Eugene to include the init.d service in his ramdisk.

NOTE: Choices 1 and 3 will work for any ROM that has busybox installed. Choice 2 will work only if the user haven't installed ICUP before (because we need the original ROM's ramdisk which supports init.d)
[Nexus S Android Development] noobiekins:
could you upgrade your kernel version to 3.2? Although I have no idea what's the difference from 3.1.6 to 3.2, if anyone knows please explain to me as well. If the difference is neglectable, ignore my request
[Nexus S Android Development] eugene373:
um, init.d is enabled via ramdisk.

3.1.X was hard enough & 3.2 is a new ballgame.. I don't have the time!

I'm only taking a week off... Thanks to the vibrant write of codec, I know how to fix the Missed called BLN :)

Battery Does Not charge to 100%, This would ruin the battery.... The 100% is cosmetic only 96% = 100% charged
[Nexus S Android Development] sean1984:
i got a reboot today when phone was charging when i was opening an app....running stock ota no overclock no tweaks
[Nexus S Android Development] eugene373:
odd, no issue at all regarding charging!
[Nexus S Android Development] mr.haqeem:
indeed...me too. no issue at all since day 1 use =)
[Nexus S Android Development] wendellc:
Me too! Going back to stock kernel.
[Nexus S Android Development] ragnarokx:
So scripts should work fine in init.d right? I'd like to disable BLD and BLN blinking with scripts in that folder. Any tips on how to do this? I've done it with other kernels/ROMs without any issues, but I seem to be at an impasse here.
[Nexus S Android Development] ncotton:
I love this kernel, combined with ASOP+ I'm up over 24 hours, moderate usage and still have 28%.
[Nexus S Android Development] tchaari:
This is a good improvement comparing it to the stock Kernel but Android OS is still eating so much. Google should really fix that...
[Nexus S Android Development] suksit:
I took the boot.img-ramdisk.gz file from Speedy-3 zip and modified it. You can try replacing the ramdisk in the zip file with this one and flash normally.

http://www.box.com/s/z732qrldfjjsxe1q4kfl

Disclaimer: *** USE IT AT YOUR OWN RISK *** :D
[Nexus S Android Development] eugene373:
update coming to night... missed calls bln is also working now.
[Nexus S Android Development] benrees21:
Can you add Simple IO Scheduler please. Also lulzactive governor. Thanks. :cool:
[Nexus S Android Development] ragnarokx:
It worked!!! Scripts in init.d now execute at boot :D

Would it be at all possible to add the above change to the next kernel update? :)
[Nexus S Android Development] allgsmnetwork:
hello friends,

my problem strange after restart fps 3d from 65 the best at 40/50 fps testing with quadrant and nemark :confused: fix problem ? help me thanks :)
[Nexus S Android Development] eugene373:
will do, odd though.. I could have sworn I fixed init.d to work already though, oh well :)

on a restart yes, fps will be low! There is still activity going on regarding loading the system / cache app's and so on.. let it sit a few minutes before firing up an benchmark utility
[Nexus S Android Development] thegtfusion:
thankss :D. what time is it in your country now?? :D
[Nexus S Android Development] eugene373:
2pm Update will be around 9pm or 10pm
[Nexus S Android Development] jurica_m:
Hi. I have one question. I have always flashed kernels when install new rom. First I have install new rom and then reboot, then go into recovery, full wipe everything and then flesh kernel and reboot my phone. So, just flash AndroidME rom and after that install this speedy kernel. Just reading about new update. Later would be new update, so just download zip file and flash in to recovery? Thanks
[Nexus S Android Development] brainmaster:
Thanks for this.

Have a suggestion - could you please disable the BLD by default?

Some users that flash my ROM with your integrated kernel are not familiar with this feature and they think that the buttons are not working.

Thanks

BM
[Nexus S Android Development] provolinoo:
+1 for bld disabled by default
[Nexus S Android Development] zadnica:
Pardon! My question is. In OP i see

Then i go to download link

And i see

and

download link -> Kernel-ICUP 3.1.6 Any Kernel-Speedy-2 -> 3.1.6_ANY-KERNEL-SPEEDY-2.zip (3.57 MB)

Where Kernel-ICUP 3.1.6 Any Kernel-Speedy-3? I'm stupid?)
[Nexus S Android Development] ragnarokx:
+2 for BLN disabled by default

Also disabling BLN blinking by default would be great (uses less battery according to Neldar).
[Nexus S Android Development] provolinoo:
Sorry but I don't agree with that.

BLN is a great feature that allows to have a perfect replacement for the missing status led on Nexus S

so I want it enabled by default

BLD instead, is a particular kind of behaviour of the soft-touch keys and a lot of users can see it like a bug since they don't know it (as reported by brainmaster)

so it's better to have it disabled
[Nexus S Android Development] adamus123:
Battery life is incredible on 3.1.6 with the stock ics. I am on 15 hrs and 71%, with music played, web browsed, email sync.... fantastic.

Looking forward to the next version - great work!
[Nexus S Android Development] S_Dot:
Are you on Speedy-2 or 3?
[Nexus S Android Development] (THE REAL) Neo:
+3 for BLN & BLD OFF by default...

These two features is unnecessary for me,and for my battery life...
[Nexus S Android Development] MFire:
Yeah me 2, BLN & BLD OFF please.

Also there is a BLD issue that keeps the capacitive keys off after you've received a notif. and unlocked the phone. One has to lock and unlock again to get the capacitive keys lights back.
[Nexus S Android Development] TheLastMirana:
is the update coming in today?

excited to try it out
[Nexus S Android Development] (THE REAL) Neo:
It just happened to me last night...scary...
[Nexus S Android Development] tchaari:
I didn't know that I have such good medium skills :D:D:D
[Nexus S Android Development] astmacca:
A few posts ago, someone was asking where to get Speedy 3?

Would like to second that query as via the download links i can only find Speedy 2.

Any help appreciated!
[Nexus S Android Development] navillos:
I'd like to see blink count and blink interval added. Also for us capable of editing scripts it would be nice to have a init.d script for controlling bln and bld. There's a nice script in simple kernel.
[Nexus S Android Development] 4I-I:
Anything about the update?
[Nexus S Android Development] Exel:
I'm sure he'll work on it soon, give him some time.

Just bought a Nexus, waiting for it to arrive, used a bunch of Eugene's stuff on my Vibrant, can't wait to try his stuff on the Nexus!
[Nexus S Android Development] obscure.detour:
I found this here.

:)

Cheers.
[Nexus S Android Development] _yaz_:
i like bln but bld annoys me (sometimes). so from me, +1 for bln and -1 for bld ;)

anyway, i've never met that "locked bld"
[Nexus S Android Development] provolinoo:
Same for me :)