yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] mrjimyjohn:
Hmm. Honestly I don't know what the up/down arrows mean on the wifi/3g icons. I always thought it meant it was either uploading or downloading data. I'm not sure what to tell you though. Did you have this problem before you flashed matr1x kernel? (When you had the stock CNA kernel)
[Nexus S Android Development] darth7:
I have the same problem. Change kernel. I'm on Air kernel now
[Nexus S Android Development] 00Droid00:
Yeah that's what I thought they meant also. This is the only kernel I have this problem on. I have tried almost all kernels on this site. But this one runs really smooth, so I'd like to figure it out. The gingerbread version of this one I never had any issues either.
[Nexus S Android Development] SA-07:
Sorry I'm not experiencing those issues at all
[Nexus S Android Development] dark06:
Those who have boot issues, i have this too.how i avoid this issue is when i battery pull, i turn on the phone via bootloader.i suspect tat the uv is causing the freezes but thats my theory
[Nexus S Android Development] LibertyMonger:
I was experiencing reboot issues with v17 on 2 different ROM's, CM9 and Gummy. Both times I flashed the ROM over and the reboots were gone and my phone ran great. I know I am supposed to mess with the voltages and stuff but I am just not experienced enough to get into that. I have faith in Matrix though and is always the Kernel I look for. I didn't have these issues with v16 and before. V16.5 I had signal issues. Thanks for the great work though MK I will be looking forward to another release!
[Nexus S Android Development] SA-07:
Lol it's really not that hard. All you need to know is how to add two numbers :)
[Nexus S Android Development] ZeppeMan:
Been running v17 for few days now on 1200/100 ondemand/noop and everything is rock stable, fast and smooth.

Keep up the great work!
[Nexus S Android Development] briggl:
I guess reflashing RoM fixes the problem because it reflashes the kernel too. Which means that you are back to kernel that comes with the RoM instead of Matr1x kernel.

Any other suggestions what could fix the problem that first boot freezes and reboots and second is normal?

PS: For me first boot after flashing is normal.

Edit: Figured out that when i use the reboot option e.g. from CM9 it boots normally, but when i power off the phone and on again it reboots once while bootanimation and second boot is normal :confused:
[Nexus S Android Development] caliban2:
Read the last 10 pages and you'll see you're not the only one. Problem not solved. Question is if it does any harm. And seems you're "lucky" that it always reboots by itself after boot #1. Me and some others got boot-freezes as well, batt-pull needed.

Now that is interesting... what goes wrong with normal shutdown then? My bet is still on one of the caches.
[Nexus S Android Development] vasilios1979:
Hello again...does anybody know if vider works with bln....all othervworks exept viber...
[Nexus S Android Development] dark06:
try turning on the phone via bootloader(volume up+power)and select reboot.i dont get freezes with this way.i notified mk about this long time ago before it was an issue for many. this only happens on matrix for me, I tried air and speedy, they are all fine.which leads me to my suspicion that its from uv.
[Nexus S Android Development] caliban2:
Tell me something new...

Reported it the first time with v16.5, with v17 more people reported it. Just entering bootloader (yes, I know how to, thx very much ^^) doesn't do the trick for me. Only wiping cache and dalvik.

It's definitely kernel-related, because simply flashing another kernel solves it. UV alone can't be the cause, last time I set the same values as glados - still boot freeze.
[Nexus S Android Development] roxxosteen:
been running this kernel with cm9 for awhile now and this issue just popped up for me with 17.0...

with 17.0 and cm9 v2 and 3 i was seeing lots of lag (settings: smartassv2, 100/1000, deep idle on, noop, no liveoc, default voltages). basically everything was freezing up: trebuchet, apps, lockscreen...just really sticky all over. i was able to switch to ondemand (all other settings the same) and its buttery smooth again. dont know why such a difference b/w governors but its great again so who cares.

thanks as always mk!
[Nexus S Android Development] R-TEAM:
Hi,

if you use NSTools then THIS is the problem.

Latest version with the "new" possibility to set various smartass(2) settings, mess complettely up with thissettings (even untouched ! ) and make smartass(2) unusable with this tool installed.-> Blame the developer , who an pure settings tool can harm the whole system to crash/reboot/unusable ...

Solutions:

Deinstall NSTools

Use another governors

Wait for an Fix for NSTools ....

If i remember correct - it is the second time, NSTools mess up with the system by SELF changing settings, the user dont need to change...

(first time i think it was voltages related ...)

So you should remember by the next problems that the dev. of NSTools dont check ther soft very properly .......................

Regards

R-TEAM
[Nexus S Android Development] j1po:
confirm it, using nstools : smartassv2 on CM9 v3.0

cpu always run on highest clock, never sleep, battery drop faster

change to another governor and wait for NSTools to fix it
[Nexus S Android Development] y3mita:
That's why I changed to CPU tuner app
[Nexus S Android Development] LibertyMonger:
Hey Mk been running v17 all day today with no issues. Ondemand governor. I haven't changed anything.
[Nexus S Android Development] aLNG:
Mk, can u fix smartassv2, because there is bug when we try to change some tunable parameters via terminal or nstool.
[Nexus S Android Development] al_madd:
Why have to blame the dev.?.he made it for free..we give a recomendation or solution..not blaming the dev..
[Nexus S Android Development] roxxosteen:
i am using nstools. i've actually noticed better battery life with ondemand so i'm gonna stick with that. after 26hrs (screen 1hr15min, wifi 18hrs) battery only down to 40%.

thanks for the tips.
[Nexus S Android Development] nodstuff:
I have the same problem with oc over 1200, and if I live oc by 105%.

What should I raise voltages by??
[Nexus S Android Development] smoke_weed:
Will this work on MIUI ICS?
[Nexus S Android Development] irtehun:
Happened again. Not sure what's happening
[Nexus S Android Development] damnmisur:
Never could live o.c. but this flies at 1200. Thanks.
[Nexus S Android Development] SA-07:
No it was to mikes question... I don't know whether it will work on .1
[Nexus S Android Development] SA-07:
If you liveoc by 105, go +30-35 across the board
[Nexus S Android Development] SA-07:
Is that 4.0.3?
[Nexus S Android Development] SA-07:
Keep going +15 with voltages and disable deep idle
[Nexus S Android Development] irtehun:
Even happening at 1000. Using bfs kernel
[Nexus S Android Development] irtehun:
Think I'll try cfs and see if its more stable
[Nexus S Android Development] nodstuff:
Nstools doesn't wanna play ball. Oc'd to 1200, raised all voltages by 25 (I know you said 30 to 35 but it only goes in increments of 25) all was good and then tried to live oc to 105% and nstools **** itself and fc'd. I think its a nstools problem.
[Nexus S Android Development] fromthestars:
Flashed 12.5 and it flashed and booted up fine. OC'd to 1200 and it felt smooth and nice. Was excited to have BLN working. But caught in a boot loop on my second reboot after installing nstools. Thankfully restoring nandroid backup.
[Nexus S Android Development] irtehun:
OK I increased voltages. Let's see if that helps
[Nexus S Android Development] SA-07:
Everyone raise all voltages by 25
[Nexus S Android Development] DaX05:
Just flashed this & screen turned off.. I received a message, noticed by the bln light & I couldn't wake it up. Had to do a battery pull.

Beamed from my Nexus S
[Nexus S Android Development] koax88:
By using this kernel,i cannot play 720p file using hw acceleration..
[Nexus S Android Development] irtehun:
Increased voltages for 1200. Turned off deep idle. Still hard sleep. On cfs now and will try it

Edit: same with cfs.
[Nexus S Android Development] nodstuff:
Smartassv2 1200max 200 min no live of and stock voltages with deep idle off. No problems and this thing flies!!!!! Oh I have an I9023 in case that makes a difference. I'm happy with this set up, it boots really fast too! Hats off to you MK!! :D

Oh and how did you get it to be <5mb?? Ezekeels is almost 15!!
[Nexus S Android Development] SA-07:
For those of you witnessing reboots, I have removed the zips and I am releasing more stable ones.

Sorry for any inconvenience
[Nexus S Android Development] irtehun:
What's smartassv2?
[Nexus S Android Development] wolfomega23:
Whoa you gotta tell me your setup

My Nexus won't hold a charge to save it's life. I don't mean to be a cell phone stalker but what is your ROM, Kernel, OC, and UV setup!?
[Nexus S Android Development] DaX05:
Could be time for a battery replacement.

Beamed from my Nexus S
[Nexus S Android Development] SA-07:
Yeah it's a bug with nstools
[Nexus S Android Development] roxxosteen:
no big deal. I'm running cm9 v3 with auto brightness edited for 50% max brightness (I only mention this cause I feel like it makes a difference). Matr1x 17, 100/1000, stock voltages, deep idle on. I don't ever use Bluetooth and I toggle wifi on when I'm at home and work and off otherwise.

Android central sells a higher capacity battery (no need for new battery cover tho) for like $50 if that's the solution you'll need.
[Nexus S Android Development] aLNG:
What I mean is, I can't change any parameters like awake_ideal_freq using terminal.
[Nexus S Android Development] mixtapes08:
I think the problem is not in nstools but the problem is in smartassc2 itself.? Hmmmm strange...

Sent from my Nexus S
[Nexus S Android Development] :
From my thread here: http://xdaforums.com/showpost.php?p=22745700&postcount=3

I have no idea if these differences are significant. But it does at least show that different values are possible and will work, at least when they are set at compile time.

Have you tried echoing the values while using a different governor, then switch back to smartassV2?
[Nexus S Android Development] aLNG:
Thanks bedalus, when I echoed using conservative it works, but not with smartassv2. It is not just this kernel I tried others too, still the same. So hope mk can figure something out :)
[Nexus S Android Development] mixtapes08:
ondemand is the best settings for me :)

Sent from my Nexus S
[Nexus S Android Development] theooo:
+1, i got amazing battery life with ondemand, using v17cfs and CNA 1.4.0

Some screenies:
[Nexus S Android Development] 4I-I:
Did you have deep idle enabled?

sent while eating an ice cream sandwich in the matr1x

I flash roms therefore i am!
[Nexus S Android Development] SA-07:
Taking feature requests for 17.5 :)
[Nexus S Android Development] DarkhShadow:
I want my phone to become a transformer

Jk, nothing I could really think to add :/
[Nexus S Android Development] mrjimyjohn:
I honestly can't think of anything! this kernel is so perfect already! :D
[Nexus S Android Development] lolokman:
Is it possible to set display fps to values below stock 56fps:confused:
[Nexus S Android Development] atlantis.mu:
Voodoo, all Ezekeel's MOD, BLN and tons of governors / schedulers!

Wow, everything in Matr1x :)
[Nexus S Android Development] krfoy:
I was fixed the issue in smartassV2.
[Nexus S Android Development] RicardoOneri:
Thank's for v17.0 working great on my Nexus S

Great stability , 0 reboots, great performance and batery life

Keep the good work!
[Nexus S Android Development] aLNG:
Great.
[Nexus S Android Development] SA-07:
Sweet, I'll add it in the next release... this fixes the lag?
[Nexus S Android Development] atlantis.mu:
Voodoo color causing green flicker!

Lucid's custom color and 65fps preferable until supercurio fix that. (I don't know for sure when that will be.)

supercurio said so himself.

http://twitter.com/supercurio
[Nexus S Android Development] SA-07:
No the 17.0 colors don't have a green flicker. I'm keeping voodoo color
[Nexus S Android Development] krfoy:
about writing tunable parameters issue, it is a bug of smartassV2. not nstools.
[Nexus S Android Development] wolfomega23:
Tried before

This Kernel was pretty decent but battery life was horrid. Anyway to make the battery last longer? I used SmartAssv2 and ondemand with Deep Idle On and Off and the battery life never showed any improvement. Anyone want to help a Padawan out?

Btw I know this may be the wrong place to post this but I think it would be better to get any pointers and advice from the maker of the kernel and any experts out there actively on this thread.
[Nexus S Android Development] lolokman:
I can get 4 hour screen on time with following settings and kangy13 rom

smartassv2, deep idle off, background process limit:3

200-1000mhz

freq arm int

1000 1175 1000

800 1100 975

400 1000 975

200 850 950

Your phone may not be able to handle so much uv as mine. But uv really helps to save battery, especially using apps/games that need heavy CPU load.
[Nexus S Android Development] ljordan2:
Also underclocking helps saving battery.

Sent from my Nexus S from Tapatalk
[Nexus S Android Development] antrobi3:
I agree,long live the Matr1x :)
[Nexus S Android Development] mixtapes08:
Cm9 ramdisk support mk will be awesome. Im still with you man and yes i did read some ns4g threads.

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Yeah haha... I am definitely considering it
[Nexus S Android Development] afzalarsalan:
It can't get much better

Maybe you could add the wifi pm_fast that Steve has in his kernel.
[Nexus S Android Development] wolfomega23:
Tried your settings and seems to work well so far thanks! But there is something that has always bothered me; why is it some phones can't handle the same OC or UV as other phones, even though they are the exact same phone model?
[Nexus S Android Development] afzalarsalan:
While the phone is the same the parts are different. All cpus aren't built perfectly. They are tested to their designed threshold and are used is passed. If they made cpus perfectly, phones would cost a lot more and take longer to produce. That is why cpus have different limits. Some CPU's are just more perfectly built than others.
[Nexus S Android Development] Andrew1998:
Help me : where i can take the "download matrix kernel" for this rom(http://xdaforums.com/showthread.php?t=1474878) , because i don't find the download of this kernel :(
[Nexus S Android Development] j1po:
below changelog and above link to source

Link to ICS version :

http://matr1xkernels.com/matr1x-kernels/matr1x-kernel-for-nexus-s-and-nexus-s-4g-ics/
[Nexus S Android Development] endursa:
request for 17.5:

https://github.com/abev66/linux_NS_ICS_vilta/commit/ad316c6049c6ce07b6bc01fd1778b8567efa9bc2

please fix smartassv2 :) so nstools can be used with it again :)
[Nexus S Android Development] DarkhShadow:
Same link was already given a few pages ago
[Nexus S Android Development] endursa:
i'm sorry, must have overlooked it :)
[Nexus S Android Development] maniac2403:
Man, I am missing your work on the GNex :P
[Nexus S Android Development] spupuz:
getting using matr1x on 4.0.4 nuhetri reloaded for now it seems stable, which governor scheduler is better for battery saving without losing smoothnes and battery?
[Nexus S Android Development] doombox414:
I don't see a download link besides the github? Or maybe its just my phone?
[Nexus S Android Development] :
Use ondemand with noop!
[Nexus S Android Development] DarkhShadow:
Hmm I have a request for 17.5 if its possible, could you add battery current data?
[Nexus S Android Development] ashwin988:
Has anyone noticed that once in a while with Deep Idle active, their Radio disables? I have noticed this twice. Was wondering if there is any solution to this? It has happened to me twice since last week..
[Nexus S Android Development] blee blee:
Best kernel ever. Keep up the good work!
[Nexus S Android Development] _yaz_:
yep, it's quite common to my crespo :'(

switch off didle

I like the stability and performance of this kernel, however I have regular boot problems. occasionally, the boot process just stops and goes onto a next loop without any reason. it's quite strange as it never goes to an endless bootloop (at least it has never happened so far). is there any rational explanation ? or is it an other kernel not recommended for crespo ?
[Nexus S Android Development] ashwin988:
Yeah, I guess I am going to start using 'SetCPU' and put profile for screen off at 200/400 and in call for the same. Do you guys think using conservative for this is the best option?

My setup is 800/1460 ,ondemand/noop and tweaked all voltages by +30. I can't use deep Idle because of the instability when it comes to my radio.
[Nexus S Android Development] zgomot:
I've read this is happens when you get really poor reception. It's supposed to be something about didle that kills radio and it's apparently 100% reproducible.
[Nexus S Android Development] RicardoOneri:
I'm using 100-1200 SmartssV2 with DeepIdle on and it working fine, great battery and performance.
[Nexus S Android Development] centroi:
hi, one question mk, can you adjust the power of wifi?? (can I?) in ics the wifi have a lot less power than in 2.3.X

is there any way to do so?

---------- Post added at 05:04 PM ---------- Previous post was at 04:56 PM ----------

reading that ondemand with noop is a good choice, what parameters do you have for ondemand??

can explain the differents sections?
[Nexus S Android Development] armoredkin:
I also use this settings. 100-800 smartassv2 n deepidle on. But sometimes my phone restart when I played music with screen off for a long time.
[Nexus S Android Development] RicardoOneri:
Try increase voltages by +25
[Nexus S Android Development] DarkhShadow:
Trying live OC for first time now :)

110% at 200/1200 ondemand

Hope its stable :)

If it is I might try 1460 xD

Sent from my ice cream powered Nexus S
[Nexus S Android Development] DarkhShadow:
Wow I think NStools went mad, had a reboot and so went to check settings only to find max and min at 1533 0.0

Sent from my ice cream powered Nexus S
[Nexus S Android Development] mrjimyjohn:
Exact same thing happened to me after I decided to try 110% live OC (from 1200) NStools doesn't seem to like this kernel...
[Nexus S Android Development] SA-07:
You do realize you can't just do that without raising voltages? My voltages sometimes can't support a freaking 110 liveoc at all times lol
[Nexus S Android Development] mrjimyjohn:
Ooh ok. lol, I'm still not quite familiar with tweaking voltages and such, and i (wrongly, it seems) assumed that 110% would be fairly low OC? anyway, can you (or anyone) suggest voltages for a 105% live OC (from 1200)? Thanks in advance :D

Also, thanks for this amazing kernel MK! :)
[Nexus S Android Development] SA-07:
I actually believe that a 105 liveoc should be fine with my voltages.... if it reboots raise all voltages, maybe +10 across the board
[Nexus S Android Development] mrjimyjohn:
Ok, thanks! :)
[Nexus S Android Development] DarkhShadow:
I raised my voltages, a lot, my phone just can't support above 1200 it seems :(
[Nexus S Android Development] SA-07:
Have you raised the int voltages as well?
[Nexus S Android Development] R-TEAM:
Hi,

very nice kernel.

btw. as of the dev. of NSTools, the voltages ONLY setable at 15mV steps!

(i believe this - an "1 step" circuite is very expensive and useless here ...)

So this should be rememberd by settings ...

(an i miss ATM only one thing in this ROM ;) ->1100Mhz Step *Hint-Hint* )

Regards

R-TEAM
[Nexus S Android Development] 93ae8074:
Hi there,

Just to let you know that if you use LiveOC patch from Ezekeel you have to use +25 steps.

Cheers.
[Nexus S Android Development] DarkhShadow:
Yes
[Nexus S Android Development] xontax:
wating for 17.5 with fixed smartassv2 gov :p
[Nexus S Android Development] k1nca:
17.5 is up : check here
[Nexus S Android Development] tma24:
random reboots. very bad kernel (v17 cfs)

//I am using stock rom 4.0.3
[Nexus S Android Development] zgomot:
This kernel is amazing, you're just doing it wrong.
[Nexus S Android Development] The1Shark:
Did you read the FAQ ?
[Nexus S Android Development] Skunk Ape1:
IMHO... Live overclocking is the worst way to overclock. For me, just choosing the CPU setting is far more stable than live oc.

____________________

Just Flash It !!!
[Nexus S Android Development] italia0101:
Can anyone tell me the stock vtages for int and arm for this kernel ?
[Nexus S Android Development] zgomot:
To my knowledge the issue is with NSTools, not with the governor, in which case how can a new kernel version fix an app issue?
[Nexus S Android Development] RicardoOneri:
Thanks for 17.5 bug is fixed in smartass2

Everthing is nice and smooth now!
[Nexus S Android Development] :
Someone's been keeping a very close eye on the download site...
[Nexus S Android Development] aLNG:
then ur knowledge is wrong :)
[Nexus S Android Development] :
matr1x v17.5 CFS updated

see here for the results!
[Nexus S Android Development] y3mita:
Yep... smartassv2 is the issue and it has been fixed.
[Nexus S Android Development] xontax:
Perfect!! :D
[Nexus S Android Development] micha3lvd:
Love your new site though it's a bit harder to find the kernels (when you posted the links here it was more easy but ok)

keep up the great work =D

messed up my ROM when I tried fixing the TOP OFF.. reflashing ROM / matr1x now.. sigh =|
[Nexus S Android Development] jerusry:
I feel like I need to flash something today... LoL

SO.. what changed on v17.5 from v17? just fixed the smartassv2 bug or what? is it worth flashing over v17? :D
[Nexus S Android Development] 4I-I:
Umm did i miss something? Whats wrong with smartassv2? Im using it without problems... will try v17.5 now but v17 was already perfect for me! Haha

sent while eating an ice cream sandwich in the matr1x

I flash roms therefore i am!
[Nexus S Android Development] DarkhShadow:
Latest NSTools broke it
[Nexus S Android Development] xontax:
No big deal flashing 17.5 Kernel, clear dalvik Cache and you are set !

Sent from my Nexus S
[Nexus S Android Development] :
It wasn't a bug with the kernel or with nstools, but with smartassV2 itself.

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] SA-07:
Don't flash the 17.5 on the site! I didn't even release it on xda yet! I have to fix some things
[Nexus S Android Development] SA-07:
Next time wait till I actually release on xda..I might change things and you will have the wrong zip
[Nexus S Android Development] :
Lol, now i have to redo the test!

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] tma24:
random reboots

yes I read the FAQ

everything by default
[Nexus S Android Development] SA-07:
Did you raise voltages? If not then you didn't read the FAQ ;)
[Nexus S Android Development] The1Shark:
LOL..
[Nexus S Android Development] RicardoOneri:
Guess you to :)
[Nexus S Android Development] SA-07:
Ok, kernel update!

I may add cm9 ramdisk ones later... we'll see
[Nexus S Android Development] 4I-I:
So if i already flashed 17.5 should i redownload it or was it fine? Haha

Thanks btw! ;)

sent while eating an ice cream sandwich in the matr1x

I flash roms therefore i am!
[Nexus S Android Development] SA-07:
Redownload :D
[Nexus S Android Development] DarkhShadow:
What was added?
[Nexus S Android Development] SA-07:
I removed a gpu tweak and added another performance tweak
[Nexus S Android Development] caleb1783:
or use 400/800 combination... smooth as butter... check my signature for details!

Sent via Divinus Nexus S...
[Nexus S Android Development] moriz1:
There are two links on the download page. which is the right one?
[Nexus S Android Development] mrjimyjohn:
one is bfs, and the other is cfs. check the OP if you don't know what the difference is.
[Nexus S Android Development] SA-07:
Yep difference is in FAQ
[Nexus S Android Development] syntax_gosong:
Uh oh... I was using this kernel before its release :D

Yeah, redownload and reflash :D
[Nexus S Android Development] SA-07:
Hehe ;)