yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] JokerAce:
Not in a proper thread to sidetrack. Leave my response to the last of it. It is running well apparently. Rumors of it being unstable, well.. rumors.
[Nexus S Android Development] eng.stk:
I'm using v22.0, very smooth and good battery life.

I'm having trouble with BLN, not working on SlimICS 4.0.4 v4.1, I got settings on NS Tools to on, but no luck.
[Nexus S Android Development] spupuz:
init.d scripts not working with this kernel? using kangyultra-ex
[Nexus S Android Development] CrackerTeg:
That's not kernel related. It's ROM related. Hit up DaxMax regarding init.d support.
[Nexus S Android Development] Pi3rluigi:
After 2 days of great work,with fantastic battery saving,this morning my phone started rebooting and shooting off by itself!

I changed anything;cleared cache and dalvik,and now it seems working properly.

I'm really confused!

Some info:

Nexus Si9020t

CM9.7

Matr1x 22

lulzactive sio
[Nexus S Android Development] alexdemonumber3:
1 day, 2 hours and 40 minutes later I'm at 45% battery life with moderate/decent usage. Am I dreaming?!?!?
[Nexus S Android Development] Rjevon:
)

Lmao!! I've definitely entered the matrix : )
[Nexus S Android Development] spupuz:
Settings please?

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] j770:
Yesterday I was almost the same result, smartasv2\noop
[Nexus S Android Development] technogravy:
That's a slim ICS issue.head to that thread for the fix, you'll also find it in the OTA app
[Nexus S Android Development] Logomotph:
I have the problem too, on stock ICS. But then again, I can't remember a matr1x version on which I didn't have this problem.

What version were you on?
[Nexus S Android Development] apatal:
Please refer to my previous post, quoted here for your convenience:

As for the stock ROM, it's been known to have ****ty USB transfer rate so don't go blaming the kernel for that.

If you guys are really in a rush when transferring files to your phone, you can always mount sdcard in recovery. Again, no one else is complaining about this so this is definitely not kernel related.

Sent from my Nexus S
[Nexus S Android Development] FirePoncho86:
Im not getting any voodoo color settings on V22...
[Nexus S Android Development] apatal:
Are you using i9020 Nexus S?
[Nexus S Android Development] grotesque02:
Sorry, can someone post me a link for deep idle fix for 4.0.4?

I'm in stock rom, thanks!
[Nexus S Android Development] mixtapes08:
http://xdaforums.com/showpost.php?p=24171689&postcount=57

Sent from my Nexus S®
[Nexus S Android Development] TigaTiger:
http://xdaforums.com/showthread.php?t=1427959

http://wildestpixel.co.uk/index.php/tweak-notes/12-didlefix
[Nexus S Android Development] mr.haqeem:
kangyultra-ex ROM..i tried INK kernel and the result is init.d support but no luck with air & matr1x kernel. jst used the same ROM. is it still related to ROM? :confused:
[Nexus S Android Development] mixtapes08:
not kernel related!

can you type this in terminal emulator

>run-parts -t /etc/init.d/

for another testing type this inside one of your init.d files

>touch /data/local/tmp/init.works

reboot

then check if (init.works) file is there on /data/local/tmp

if its there your init.d works
[Nexus S Android Development] mr.haqeem:
it jst say no such file or directory..hmmm :confused:
[Nexus S Android Development] alexdemonumber3:
1200-200 smartassv2/noop/deep idle on
[Nexus S Android Development] mixtapes08:
Try the other test

Sent from my Nexus S®
[Nexus S Android Development] caliban2:
Did you give root-permission to terminal before you tried it? (Type su in terminal)
[Nexus S Android Development] caliban2:
It is kernel related, I already reported this two weeks ago but it's so much easier to put it on the rom...

Did both your tests, and they work. So everything's fine with init.d on cm9, right? It's the kernel-settings inside the nstools-script that aren't applied anymore. Gov stays on ondemand, should be smartassv2. If I change voltages they get applied though.

It all started around matr1x v20, v20.5. You should know from beta that this is the time other things started to go wrong as well and that v22 is a beefed up 19.5 with some of the later tweaks. Chances are good one of them overwrites governor during boot AFTER init.d has run. Or something in boot order changed (roms) and mk didn't adjust. (Something like the wifi-module on cm9 a few months ago)
[Nexus S Android Development] mixtapes08:
i tried those two on aokp as well and it works too. So init.d works right ?anyway I didn't try nstools script yet though.

Sent from my Nexus S®
[Nexus S Android Development] caliban2:
Well, try it then. But if you're still using ondemand, set another gov first.

And like I said, if I change voltages in nstools, they get applied. It's the gov-part that is ignored/overwritten. So the script half works.
[Nexus S Android Development] mixtapes08:
Nstools working fine for me. Im using smartv2 also.

Do me a favor and do this.

Set nstools and your configs

Tick set on boot and use init.d

Reboot

Go to your init.d script

Modify 99nstools

Delete unnecessary scripts under first line just like this

Then go to nstools untick set on boot

Reboot

go to nstools again and check if your config values are still there.

Let me know if it works it seems that nstools is the problem.

Sent from my Nexus S®
[Nexus S Android Development] caliban2:
Nope, still the same.

It's just the gov that gets reset, everything else is there. Maybe it's cm9's settings that interfere, it has a rudimentary kernel control as well. Aokp doesn't, right?

Mathkid, you still have my boot-logs?
[Nexus S Android Development] mixtapes08:
Could you try renaming the nstools script just like what i did . delete the 99nstools.bak too just too ensure that it will not interfere.

Btw aokp has cm like settings too

Sent from my Nexus S®
[Nexus S Android Development] xdoit:
There are some pause phenomena when playing music with google play music.

The sound effects is ON.

- google stock rom 4.0.4

- cfs v22.0 kernel
[Nexus S Android Development] mixtapes08:
Does yoir deep idle enable?

Sent from my Nexus S®
[Nexus S Android Development] sdhanjal15:
Don't leave mk! Jelly beans coming!
[Nexus S Android Development] xjerlzx:
I had same issues, deep idle enabled but in all past versions I never had that. Issue
[Nexus S Android Development] :
Are you using any mod like the low latency mod?
[Nexus S Android Development] Paragon_X:
So I've been rocking v20 since I have the amoled paired with the new CM9 rc1. Anywho, it worked terribly, quite a bit of lag and was pretty much unbearable. So I switched to v22 and it's much smoother but in the process of testing battery life. Also I found v20 worked well with other ROMS beside CM which was weird, best was with Gummy but Gummy stable is so outdated I didn't bother, maybe I should have tried nightlies... anywho, that's my exp will report back later with battery life
[Nexus S Android Development] xjerlzx:
im not,

i guess its the governor i changed to ondemand/noop 100-800 and it seemed to be resolved.

initially it was smartassv2.
[Nexus S Android Development] aic719:
Voodoo is coming on v13. Be patient.

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] ValenteL:
I installed on a 4.0.3 rom your bfs 12.5 kernel. My score AnTuTu is the better of all rom i have tested 3710. But... the camera video don't work. I film 5 seconds and stop FC. I tested the kernel on 3 rom's 4.0.3 and the same at all.

After I installed the Glados bfs 2.2 and no problems whit camera video on 3 rom's. I film very well. The Glados is 3.0.8, Your 3.0.13. A version problem ?

Thanks
[Nexus S Android Development] KBanause:
Video recording is a known bug and afaik mathkid already mentioned that it will be fixed in the next version.

Greetings,

KBanause
[Nexus S Android Development] SA-07:
Yeah everything is in but there are some oc problems that I need to fix..
[Nexus S Android Development] Neuron:
some voltage problems as well.. i applied the same voltages as on the gb kernel (only some where 5-10 more mV) BEFORE OCing on the ICS and it just suddenly froze and then it would just instantly freeze after each boot
[Nexus S Android Development] SA-07:
Nope voltages are fine
[Nexus S Android Development] kramer987:
been running this for a few days now. battery life is excellent, or seems to be for ICS. i never run OCd so i can't tell you if there is any stability, but at 1000/10000 the stability is 100%. havent had a reboot. the ONLY issue i saw with OC is when i tried to go up to 1.4 it just killed the phone. went into boot loop.
[Nexus S Android Development] SA-07:
You can raise the voltage.

Just check my faq ;)
[Nexus S Android Development] joaoennes:
This kernel is very stable for me, as usual. I only miss the voodoo stuff.

P.S. CFS seems to work better for me :)
[Nexus S Android Development] SA-07:
Yeah voodoo coming in 13.0 ;D
[Nexus S Android Development] X1111:
we are waiting for 13.0 hopefully :rolleyes:
[Nexus S Android Development] nodstuff:
Voodoo!!!!!!!!!!!!!!!!! :D
[Nexus S Android Development] SA-07:
now, for the moment you have been waiting for.

v13.0!!!!!!!!

for the wifi problem with the i9023 Iran users, I would suggest loading that .txt file into a .sh script with script manager.

I would also like to thank nodstuff for helping me with the git merge conflicts when loading voodoo in ;)
[Nexus S Android Development] gavingreystone@gmail.com:
Been waiting for this thanks :)
[Nexus S Android Development] iGoogleNexus:
Flashed it and everything is freaking awesome... =] MK... badass

-Google
[Nexus S Android Development] irtehun:
Bout time MK ;)
[Nexus S Android Development] SpOuK-3-:
Just got a reboot... no OC, but deep idle is activated...
[Nexus S Android Development] SA-07:
Just check my FAQ...
[Nexus S Android Development] SpOuK-3-:
Which part? :)
[Nexus S Android Development] mr.haqeem:
it say..not found. dats all i know coz not good with coding. jst follow your instruction and thats the result.

---------- Post added at 12:02 PM ---------- Previous post was at 11:55 AM ----------

now what is this...some people say not related and some say it related. which one is true? from my test and playing with many kernel,i feel it related but im not good enough to say its REALLY related or not. so i think u can give better xplain for this probs :cowboy:
[Nexus S Android Development] Paragon_X:
I hate to be a bother. But MK is there anyway you can do a updated version of v20 for the amoled users. I know this request was put forth and ultimately denied but I thought I'd shoot it again. Comparing it to v22 the lag on certain ROMS and popular ones is quite noticeable, in addition to the battery drain. Nothing crazy mind you, but clearly v20 does serve better unfortunately slightly under performs =/ and I can live with it, just thought I put it out in case because you never know =)
[Nexus S Android Development] SA-07:
I'm am amoled user and I don't have any lag... so no

Feel free to stick to v20
[Nexus S Android Development] rasengan82:
Man, is it possible to have a fastboot flashable image for the matrix kernel?
[Nexus S Android Development] SA-07:
Sure, what do you need it for?
[Nexus S Android Development] 309041291a:
Is MK going to make one final build for the upcoming JB?

It's really going to suck when JB gets released. I have ton of MODs, Apps, kernels, and ROMs that won't work :(. Ill be so tempted to upgrade but I'll have to leave everything behind again (GB -> ICS)...

Nexus S (GSM i9020a)

Paranoid (14.a Hybrid - 4.0.4)

Matrix Kernel (CFS - 20.0)

Intellidemmand (800/100)

Live OC (105 - 800/1000)

Deep Idle (On - Noop)

BLX - 96
[Nexus S Android Development] rasengan82:
I'm just wondering if you flash the Matrix kernel img with fastboot and then flash the stock 4.0.4 boot.img, would that replace the matrix kernel with the stock kernel? Would this work even if we flash Matrix with the CWM flashable zip?
[Nexus S Android Development] SA-07:
??????

I don't understand... why don't you just flash the CWM zip.... :eek:

Are you trying to troll me? lol
[Nexus S Android Development] rasengan82:
LOL nvm. I think I smoke too much lol
[Nexus S Android Development] Paragon_X:
No worries. I reflashed v20 over v22 and it seems to be a bit better. Maybe I had to let the ROM go through the motions n such but it's working well so yah we can disregard my request as you've already done lol =D
[Nexus S Android Development] grotesque02:
Thanks!

With this fix I have Top=ON>Top=OFF, is normal?
[Nexus S Android Development] Sesese87:
Try to fix permissions in rom manager and reboot your phone
[Nexus S Android Development] caliban2:
Top on is used if Bluetooth is enabled or GPS is in use.
[Nexus S Android Development] LibertyMonger:
Kernel v22 has been great, no issues except NStools settings do not stick. I am running Kangy Ultra.
[Nexus S Android Development] sdhanjal15:
Reflashing it fixed it for me
[Nexus S Android Development] apatal:
No problems here with NSTools. Make sure you have check set-on-boot option in the settings tab. :)

Sent from my Nexus S
[Nexus S Android Development] LibertyMonger:
I have reflashed a few times, not because of this but it hasn't fixed it. The only thing I didn't do is a clean flash. So maybe I will try that.

Yes it is checked but thanks anyway.
[Nexus S Android Development] jark99:
What are some good voltages if running a 1000/200 setup? I can never understand how much to under volt to get good battery life. -50? -25? -100? Ughhh

Sent from my Nexus S
[Nexus S Android Development] Pi3rluigi:
If I don't misunderstod is alredy undervolted;I have to rise +25 to prevent crashing as my Nexus is one of those who don't like undervolted kernel;you can try -25 steps untill it crashes,when it happens you 'll know the limit of your phone
[Nexus S Android Development] explorer-10:
anyone tried playing Sonic4Ep2 yet? i dont understand why it lags most of the time whereas a game like Nova 3 doesn't quite lag as much, only small hiccups here and there

im currently using one of the slightly older kernels, v21.5

edit: also, this is one of the first full-fledged 2D/3D android games to use bluetooth! =)
[Nexus S Android Development] CrackerTeg:
Just another random reboot during a 12 minute call. This time on v22. I'm at a total loss here.
[Nexus S Android Development] SA-07:
Me too... since you didn't post any more info xD
[Nexus S Android Development] CrackerTeg:
What kind of info? Governor, scheduler, things like that?

SmartassV2, deadline, 1200/100, no live oc. Deep idle enabled. Stock settings for voltages and the governor. I don't have a logcat though.
[Nexus S Android Development] caliban2:
There are no stock values for 1200 - have you tried upping its voltage? And what do you mean by "stock" - mathkid's values or google-voltages?

I have the same settings as you, except 1000/100 and smartassv2 a bit adjusted. No freezes here (longest call: 1 1/2h with my mom. Felt like 3 though... ^^)
[Nexus S Android Development] CrackerTeg:
MK stock.
[Nexus S Android Development] apatal:
lol at this. :D

@CrackerTeg: May I suggest trying a different governor? Say try this setup first:

deadline

ondemand

100/1000

15000 sampling rate

98% up threshold

Let us know how it goes. :)

Sent from my Crespo
[Nexus S Android Development] CrackerTeg:
See, that's the thing. That has been my setup since v14. I hate to change based on that alone. I can't fathom or remember where the problem started. Or which version started acting up on me.
[Nexus S Android Development] mixtapes08:
Did you flash matrix over the top of another kernel?

Sent from my Nexus S®
[Nexus S Android Development] explorer-10:
This?
[Nexus S Android Development] caliban2:
You see, v22 should've fixed all reboot/freezing-issues, and so far it has. Until now you're the only one reporting problems. So make sure it's the kernel and not something else:

- rom-related? How long since your last full wipe? Bug in rom? Did you ever change roms without a full wipe? (i.e. stock -> cm9)

- dialer-app? Have you tried deleting data of it or tried another dialer, just for testing? (i.e. exdialer)

- overclocking: just for a change, try with 1000/100

- voltages: matr1x comes undervolted, especially INT (ARM not so much). Up them +25mV. Real stock voltages can be found in post#1 of bedalus' batt-thread.

I know this sucks because your setup was stable before, but as long as you're the only one having these problems, you have to rule out all other causes.

Edit:

What about cfs vs bfs, have you changed the kernel version?
[Nexus S Android Development] jimdem:
Hello. I am using matrix 22 cfs with aokp b40 for a week now and there was no freeze or reboot. Stable as rock! However yesterday when the phone booted and when I was at the sim unlock screen, it hanged and soft rebooted. Then it was working fine. The same thing happened today also at the sim unlock screen. I have stock voltages, 100/1000 on demand /deadline, deep idle on
[Nexus S Android Development] xdoit:
Deep idle is OFF.
[Nexus S Android Development] apatal:
This used to happen to me before on AOKP. I think I solved it after a clean install. Again. like the post above, this incident doesn't seem universal to all users so you have to try and rule out other possible causes before concluding it's a kernel issue. :)

Sent from my Nexus S
[Nexus S Android Development] VaksenDK:
Maybe not to all users, but exactly the same thing has happened to me.

I am also on CFS 22 and AOKP b40. (And MK voltages, 200/1200 SmartAssV2, deep idle off.)

However I blame AOKP (and myself) as it only happens, when I update to a new AOKP build and only on the first boot on the new build, and I never do a full wipe when updating AOKP (did of course a full wipe on first AOKP install coming from stock ROM).

And in daily use V22 is doing really great on my i9023. Just as rock stable as 19,5, and even seems both faster and less battery consuming. V22 is really superb work, MK, Thanks for your great work.
[Nexus S Android Development] CrackerTeg:
No. Always used matrix. The only kernel I would've flashed over would be the stock kernel included in the ROM.

-One week since my last full wipe. No. I haven't changed roms without a full wipe. Ever.

-No. I haven't. Stock dialer on every single ROM I've tried. My current one (see sig) has been the most stable and fastest for me.

-I'll try not overclocking but since it's so random but that may not even be the culprit.

-Again, I've always run matrix and I'm well aware it's undervolted and the phone has taken it just fine until recently.

-I've always run cfs versions.

Here's what I need to ask to completely rule out the kernel in my mind. Any for you guys with a custom ROM, do you leave stock background processes limit or do you cap them?
[Nexus S Android Development] JokerAce:
Not recommended to use the battery to below 30% if you want the most number of cycles your battery to sustain. #Justsaying

---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------

I am facing same problem with freezes/sleep-of-death/reboot with OC. Trying the +25mV across board. Let's see if it helps..
[Nexus S Android Development] CrackerTeg:
I went back to my normal settings except for the OC. Its still quick as hell but I also decided to use sdhanjal's smartass settings which jokerace quoted above. I figure I try one thing at a time rather than try everything at once and not know what the culprit was. It just sucks about the random reboots during calls because they are just that. Random.
[Nexus S Android Development] anshumandash:
lags on V22

I have flashed the cfs v22 and used Matr1x for the first time. I am experiencing lot of lag on certain screens like dialer, SMS compose, facebook app sometimes give 50% blank screen and 50% appear with content. SMS app has crashed multiple times. some of the games freeze in the loading screen for sometime and then work fine. Have not faced any re-boots yet. Using it since last 30 hours or so.

My setting: smartassv2, noop, CPU 200-1200, have tried deep idle on/off without any change, live OC on, default kernel voltages. I am on stock 9020T ROM.

I had earlier used SGs kernel without any problem. had even overclocked up to 1320.
[Nexus S Android Development] michalurban:
Strange thing, during the v22cfs update I did the usual (wipe cache, wipe dalvik, flash kernel) but with the same rom and kernel settings (loaded a previously used and saved Nstools setup) I disconnected the phone from a charger ... to find out 4 hours later that I was at 74 percent of battery without any use. Now Im back on my saved v20cfs ROM manager image (made just prior to the kernel update) and charging just to make sure it wasnt ROM- or app-related. Ill let you know.
[Nexus S Android Development] xjerlzx:
Let it run for a while and it will b fine
[Nexus S Android Development] mixtapes08:
Dl betterbatterystats to know what's draining your phone

Sent from my Nexus S®
[Nexus S Android Development] apatal:
Since it's your first time using matr1x. Make sure you cleaned out your init.d folder in /system/etc. As an option, you can also try fixing permissions in recovery, and if you're desperate, you can try to reflash your rom then matr1x then reboot after fixing permissions.

Sent from my Nexus S
[Nexus S Android Development] TigaTiger:
On a quick note, dont you have to reboot atleast once before you flash the kernel? or else there might be problems?

eg. Flash rom -> Reboot -> Flash kernel -> Reboot -> Bobs your uncle.
[Nexus S Android Development] caliban2:
Don't forget to sprinkle the phone with blood of a black rooster and light a candle. AFTER you flash the rom, but BEFORE you reboot.
[Nexus S Android Development] :
There was a wave of this going around for a while, but the best thing to do is flash the kernel right afterwards.
[Nexus S Android Development] anshumandash:
init.d folder is empty. It is not easy for me to flash the ROM. I am on google stock ROM 4.0.4. I don't think there is a flashable ROM available. There is one available for 4.0.3, but not sure if my phone will allow to flash a lower version of ROM.

I increased the OC to 1300 and there seems to be some improvement. I will monitor and will try to fix permissions if issue persists.

My old kernel from SG had default bus speed of 220 MHz. That was fast & smooth. I tried using Live OC of 110% & 105% with base CPU speed of 1000 MHz, but the phone started rebooting with either of the settings.

Not sure if there is anything else. Will 1300 OC drain battery faster?
[Nexus S Android Development] CrackerTeg:
Yup. I normally ran 1200 and would get a days use but I dropped yesterday to stock speeds and I now get over 36 hours with same use. I haven't noticed a drop in speed either.
[Nexus S Android Development] rrohanjs:
got this with matrix 19.5 and 20 .. cant duplicate it now .. weird
[Nexus S Android Development] mixtapes08:
Stop using stock rom for god sake. There are many stock like roms here. Try it and see the results.

Sent from my Nexus S®
[Nexus S Android Development] sdhanjal15:
Goodbye amazing battery life! Going to stock to get my ota!
[Nexus S Android Development] CrackerTeg:
For example, Rascream. Been the best one to me yet.
[Nexus S Android Development] apatal:
+1 ;)

Sent from my Nexus S
[Nexus S Android Development] explorer-10:
anyone tried playing Sonic4Ep2 yet? i dont understand why it lags most of the time whereas a game like Nova 3 doesn't quite lag as much, only small hiccups here and there

im currently using one of the slightly older kernels, v21.5

also, this is one of the first full-fledged 2D/3D android games to use bluetooth! =)
[Nexus S Android Development] sdhanjal15:
Try updating the kernel and maybe try bfs version
[Nexus S Android Development] stewarta:
+1 I agree totally with this procedure. Tried and proven.
[Nexus S Android Development] anshumandash:
Not a good time to try a customer ROM though it would be better than stock ROM. It is time to wait for Jelly Bean. Then may be once a custom ROM for Jelly Bean comes out, it would be good to try.

I am hoping Matr1x will have a really good Kernel once Jelly Bean is out :D