yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Harbb:
The Nexus S battery uses a method of finding the state of charge that is convergent. After rapid changes switching between on and off with varying power consumption it often gets confused and gets quite inaccurate. As time passes in a more stable environment it will get closer and closer to the true state of charge.
[Nexus S Android Development] Shadow-Nexus:
I still get the green screen :(
[Nexus S Android Development] mrjimyjohn:
Make sure your brightness is set to min. 25%
[Nexus S Android Development] Shadow-Nexus:
It was anyway I went back to trinity I can't handle the green screen
[Nexus S Android Development] heinst:
Are you using the latest matrix? 17.5 should have fixed it.
[Nexus S Android Development] mrjimyjohn:
Suit yourself :P
[Nexus S Android Development] caliban2:
either that or, more possible in my opinion:

matr1x uses the cosmetical blx-mod, glados doesn't. guess that's the difference.

glados shows the real batt-status (full around 96%), while matr1x stretches this and shows 100%. as I said, this is pure cosmetics.
[Nexus S Android Development] heinst:
I agree. All the android batteries for whatever reason charge 95-96% the kernels that show 100% are meant to show that to keep the user at ease and not make the worried haha
[Nexus S Android Development] SA-07:
Until v18.0 is released, here are 17.5 CM9 ramdisk versions!

CFS: http://goo.gl/04gt1

BFS: http://goo.gl/mSarU
[Nexus S Android Development] mixtapes08:
Lets see for the other kernel update. You know who ;)

Sent from my Nexus S
[Nexus S Android Development] Shadow-Nexus:
Hey which version of matrix is better for battery saving
[Nexus S Android Development] nexus_junkie:
Users took a dim view of your post. :( It is this thread's kernel that imitated Trinity's CM9 ramdisk version!
[Nexus S Android Development] mixtapes08:
I think cm9 ramdisk source are open source right?

Sent from my Nexus S
[Nexus S Android Development] nexus_junkie:
You are just pulling the noose around your own neck. So what's your purpose? What do you want to say? Is it aimed at the specific kernel?
[Nexus S Android Development] mixtapes08:
Superb smoother and much faster in cm9 rom... :)

Sent from my Nexus S
[Nexus S Android Development] theooo:
Sorry, but what is the difference between normal ramdisk and cm9 ramdisk?
[Nexus S Android Development] mixtapes08:
You can use it in the 3.4 and latest cm9 builds. Its much faster than any kernel versions. Note its for cm9 only ok.

Sent from my Nexus S
[Nexus S Android Development] theooo:
Thanx for ur quick response dude :D

I see, but can we also use normal ramdisk version on CM9?

Or is this the reason i got pretty bad performance while using normal ramdisk version of this kernel on cm9 v3.4??
[Nexus S Android Development] mixtapes08:
Yup u can use anykernel version but will cause some performance decrease.

Sent from my Nexus S
[Nexus S Android Development] theooo:
Ahhh, i got it. Thats why cm9 default kernel is smoother and faster compared to normal ramdisk version of this kernel :D
[Nexus S Android Development] mixtapes08:
U got that right :)

Sent from my Nexus S
[Nexus S Android Development] al_madd:
matr1x kernel default settings is UV..but glados using stock voltages..
[Nexus S Android Development] mixtapes08:
Its because of the cosmetic 100% battery fix by matrix. Its not bec of the uv of matrix.

Sent from my Nexus S
[Nexus S Android Development] cowst:
thanks for the answers guys, i suspected it was that, but using a proportional scale, 100:95 should not give a 75:70, unless it is not proportional, but just adds a 5%, meaning that your phone will turn off at 5% higher than glados for example.

another thing i noticed, is that i went to sleep for around 8 hours with battery 73%, and i got up with 72%.

i always noticed more than 1% consumption overnight, is 1% really reasonable?
[Nexus S Android Development] mixtapes08:
Thats good battery btw. Your deep sleeping just like your phone do. ;)

Sent from my Nexus S
[Nexus S Android Development] 4I-I:
Would cm9 ramdisc version give better performance on cybermod v9?

Just wondering.. normal ramdisc version is great already!

sent while eating an ice cream sandwich in the matr1x

I flash roms therefore i am!
[Nexus S Android Development] mixtapes08:
Yes

Sent from my Nexus S
[Nexus S Android Development] RicardoOneri:
Thank's working great like allways Mk: )
[Nexus S Android Development] italia0101:
What kinda live oc you lot rocking ? State vtages as well please
[Nexus S Android Development] cowst:
is there any 4.0.4 cm9-based rom?

otherwise I am conflicted between 4.0.4 and a cm9-based+ramdisk.

with matrix of course :)
[Nexus S Android Development] tjackbjorn:
what is ramdisk...? ^^
[Nexus S Android Development] foxmolder1985:
Just flashed on my pixelrom. Thank you for your work!
[Nexus S Android Development] Si_NZ:
I see quite a few people having this problem now, including myself. I use a rooted stock ROM on i9020T. I've even tried a fresh install by factory reset + format /system + reinstall stock 4.0.3 ROM. After a fresh install, I immediately open up the camera app without any configuration at all, and this problem pops up.

The camera is totally unusable with this kernel. Not only you would see green lines in preview, photos taken would often contain large area of pure grey.

I wanted to use this kernel, but this problem is really preventing me from using it :(

Strangely, no other kernel has this problem.
[Nexus S Android Development] Skunk Ape1:
Not having that problem and have never had it with any of the matr1x kernels. Photos taken in both well lit and dim to dark have always came out fine.

---------- Post added at 06:16 AM ---------- Previous post was at 06:11 AM ----------

yes it it. I often get 0% loss when phone is sleeping for as long as 6 hours when using the Wheatley Gov and deep idle. Of course I shut off all data including wifi when I sleep.
[Nexus S Android Development] Realtyem:
Hey MK been enjoying this build for awhile now. Great job on keeping the pieces put together this well. I have a small request for the next build. Could you turn on swap please, I would like to test something in the VM that I was reading at kerneltrap. Much appreciated.:)

Edit: plus it appears that your 05zram script isn't doing anything because there is no swap. Just a little heads up there
[Nexus S Android Development] foxmolder1985:
camera works really good here too. I haven't the problem mentioned above.
[Nexus S Android Development] cowst:
I meant that. seems to guarantee better performance
[Nexus S Android Development] foxmolder1985:
Hello, anyone has my same problem? When I try to set CPU to 1300 or 1200,or change the governor the phone reboots, and it reboots until I do not change the governor and cpu settings to the standard.

What may it be?
[Nexus S Android Development] al_madd:
Maybe it will helping if you mentioned

ROM,

version of kernel BFS,CFS

OC using what app or terminal emulator??

me using bugless beast with v17.5 CFS having no problem changing gov or OC using nstools...
[Nexus S Android Development] ZeppeMan:
For some reason I had huge batterydrain since yesterday. I went from 100% to 61% over the night while doing nothing with it.

I rebooted to see if it would be fixed, but the problem remained. I just reflashed everything with full wipe and the problem seems to be fixed for now.

I don't know if it was your kernel or maybe the ROM (CNA 1.4), but it was very strange. Never had this before.

EDIT:

Problem is not fixed :( Going to try another kernel/ROM later to see if it fixes my issue.
[Nexus S Android Development] foxmolder1985:
Hi, I'm using pixelrom 1.60 v17.5 CFS scheduler i've tried is vr and deadline, when OC to 1.2 or 1.3 it selfreboots. When I have normal settings, like 100-1000 everything goes right
[Nexus S Android Development] saranyan:
Raise the voltages. Or your phone cant handle OC
[Nexus S Android Development] foxmolder1985:
It has been 1.1 ghz for months with another kernel. Maybe it's the voltage, but I don't know how to set them up, and I'm also afraid to make trouble :o
[Nexus S Android Development] pilspeda:
v18 ramdisk for CM9 really made a difference.

Extremely smooth.

Thanks !
[Nexus S Android Development] al_madd:
just use nstools from play store to increase volt...it is free...

dont worry..If anything wrong with your phone..you can buy a new phone..:p:p:p
[Nexus S Android Development] darknight74:
Hi all.

I'm enjoying matr1x on aokp 27 using nstools to change governor (smartass2) and scheduler (noop)

Btw My phone locks on boot unless I remove battery or i launch bootloader and reboot from it.

Any idea to fix or debug this issue?

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] cowst:
could you tell the difference between that and a 4.0.4 ROM?

i know it is not possible to give an exact estimate, but we see that 4.0.4 roms are better in benchmarks, so it would be nice to know how is the feeling compared to one of the top 5
[Nexus S Android Development] mixtapes08:
This is a kernel thread not a rom thread btw :p. If ur on cm9 benchmark doesnt matter. U can feel that is much quicker than any other kernels.

Sent from my Nexus S
[Nexus S Android Development] caliban2:
is the latest version really supposed to only have an effect on cm9? call me crazy, but everything feels just a tad smoother on my stock-4.0.4 as well... :p
[Nexus S Android Development] cowst:
i know it's a kernel thread, but:

1 - you pointed out something about the performance with ramdisk that could be generalized

2 - the answer to my question still affects my kernel choice

benchmark for cm9 indirectly matters, because the top roms are all on 4.0.4, no cm9 up there, and i tried roms cm9-based and i found all of them visibly slower than those with 4.0.4 i tried.

however for the same rom i found default kernel and matrix way faster than glados.
[Nexus S Android Development] mixtapes08:
For me benchmark doesnt matter i did got some pretty high benchmark on other kernels but ui experience is much betterfor me. Maybe i will try 4.0.4 some other day and ill report back to you.

Sent from my Nexus S
[Nexus S Android Development] tjackbjorn:
is the ramdisk version onlt for cm9?
[Nexus S Android Development] SA-07:
Sorry for the delay! I'll work on the kernel asap
[Nexus S Android Development] insomnia48:
Back from franco's? ;)
[Nexus S Android Development] insomnia48:
Enough LOLs. Get your ass down to work. We need an update. NOW :eek:
[Nexus S Android Development] italia0101:
How far can you safely live oc with this ? I'm currently running 110% .. wondered it people are going higher
[Nexus S Android Development] RicardoOneri:
From Stock voltages? I think 110 the max with stock
[Nexus S Android Development] tjackbjorn:
What's the meaning of Live OC? noob question...
[Nexus S Android Development] RicardoOneri:
Livre OC means Live Overclock, is CPU And BUS speed clock.

When OC value is changed, the minimum and maximum frequency limits set by the user are adjusted according to the new frequencies

In '/sys/class/misc/liveoc' change the performance by passing a value from 100 to 120 to 'oc_value' (100 = stock performance, 120= +20% performance; 100 is default). The bus speedand frequencies for all states will be adjusted accordingly.
[Nexus S Android Development] mixtapes08:
Gonna up this wonderful kernel :)

Sent from my Nexus S
[Nexus S Android Development] SA-07:
looking for testers! pm me email id
[Nexus S Android Development] nodstuff:
Hey guys, just thought I'd post one last time before I head off to the gnex forum, just want to thank you all for good debates and intelligent conversation.

And most importantly MK95 for his great kernel, it's the ****, always has been since gb days!

So anyways best of luck guys, maybe see you all soon on the other side!! :D
[Nexus S Android Development] satthienthan1:
PM already. Send me asap ^^
[Nexus S Android Development] mixtapes08:
Thats so sad were loosing people here good luck on ur new phone

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Yeah guys, I need to move on as well. Good luck to everyone! :)
[Nexus S Android Development] DaXmax:
Man, dont tell me yur also moving on to Gnex?
[Nexus S Android Development] mixtapes08:
I think. Move on to v18? :-)

Sent from my Nexus S
[Nexus S Android Development] al_madd:
Oh noo....thats mean no more matr1x kernel for nexus s??
[Nexus S Android Development] SA-07:
Yes, move on to v18 ;) hehehehe
[Nexus S Android Development] y3mita:
brother you made me laugh! good sense of humor!
[Nexus S Android Development] zipredictive:
"Oh s#@§!"

Mom: "hey whats wrong?"

"nothing mom everything is ok!" :D
[Nexus S Android Development] RicardoOneri:
Funny as allways :)

Allready PM you :)
[Nexus S Android Development] qaz2453:
stupid question:

will this work with a 4.0.4 ROM?

thanks
[Nexus S Android Development] SA-07:
Yea
[Nexus S Android Development] qaz2453:
thanks :D:):)
[Nexus S Android Development] RicardoOneri:
Will we get an update today or tomorow MK? (If everything went right with tests)
[Nexus S Android Development] DaXmax:
ETA :- 21 December 2012
[Nexus S Android Development] thegtfusion:
Lolllll
[Nexus S Android Development] satthienthan1:
yes.Work with 4.0.4
[Nexus S Android Development] caleb1783:
lol isnt that supposed end of maya calendar?

Sent via Divinus Nexus S...
[Nexus S Android Development] y3mita:
or end of world ;)
[Nexus S Android Development] heinst:
I needed some stability in my life so I flashed this kernel haha
[Nexus S Android Development] armoredkin:
I thought it was 12 December? Is it postponed? yeay we can flash another 1 or 2 kernel version lol
[Nexus S Android Development] DaXmax:
end of maya calendar not WORLD end from what i know. And this is crazy, why we suddenly talked bout world ending? O.o
[Nexus S Android Development] mixtapes08:
No.. thats my bday. :)

Sent from my Nexus S
[Nexus S Android Development] DaX05:
Seems like Matr1x 18.0 is up:

http://downloadandroidrom.com/file/matr1x/NexusSandNexusS4G/18.0

Beamed from my Nexus S
[Nexus S Android Development] DaXmax:
Holy fishballs. Its out.

BFS ONLY, CFS no mirror. :/
[Nexus S Android Development] :
http://www.mediafire.com/?88zx58682mzqg8z

This appears to be the mirror for v18.0 CFS
[Nexus S Android Development] SA-07:
Huh? works fine here..
[Nexus S Android Development] SA-07:
CM9 Ramdisk versions!

CFS: http://goo.gl/TkNFf

BFS: http://goo.gl/8JLn5
[Nexus S Android Development] DaXmax:
Not Found for me.
[Nexus S Android Development] SA-07:
Kk, mirrors are fine
[Nexus S Android Development] SA-07:
CM9 Ramdisk versions!

CFS: http://goo.gl/TkNFf

BFS: http://goo.gl/8JLn5

(deliberate double post! :D)
[Nexus S Android Development] antrobi3:
18.0 versions are up !
[Nexus S Android Development] DaX05:
Appreciate that. :D

Beamed from my Nexus S
[Nexus S Android Development] :
Matr1x v18.0 CFS benched!

Results here: http://xdaforums.com/showthread.php?p=23598175
[Nexus S Android Development] al_madd:
MK..

I think you forgot about cleaning script right??:D:D:D

Or you just get rid of it for some reasons??
[Nexus S Android Development] mixtapes08:
Yup he did.. dalvik and nand still there in init.d i just deleted it.

Sent from my Nexus S
[Nexus S Android Development] sperelli:
Hi mathkid, do you think i need this version on Cybergr v9 rom?
[Nexus S Android Development] samarium:
Thanks for the update.

I looked at both 18-cfs and 18-cfs-cm9, and /proc/config.gz seems to have disappeared, while it was there on 17.5.

Nor can I see in in the github root?

Can you point me to .config somewhere please?
[Nexus S Android Development] :
Try it. Check it doesn't break Bluetooth

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] sperelli:
why could it happen?
[Nexus S Android Development] Psygen:
What do you mean by SWAP? More RAM? Is it a true SWAP?
[Nexus S Android Development] tonylee83:
Which one should I flash for aokp?
[Nexus S Android Development] mixtapes08:
The one in the site. Check the op

Sent from my Nexus S
[Nexus S Android Development] pilspeda:
Thanks for the update
[Nexus S Android Development] Oodie:
Ok . 18's up . Gonna try it right now . Thanks mathkid .

..Generated from OodieMiui via Tapatalk..
[Nexus S Android Development] Shadow-Nexus:
does v18 fix the green screen?
[Nexus S Android Development] DarkhShadow:
You mean green flicker? Change v1 gamma hack to 2.3.3 defaults and poof

Sent from my ice cream powered Nexus S
[Nexus S Android Development] heinst:
In the voodoo control panel that is. Green screen should have been fixed in 17.5
[Nexus S Android Development] SA-07:
No the cleaner is there.
[Nexus S Android Development] al_madd:
No green flick for me since V17...

This my antutu bench mark..

default voltage , default gov and I/O

min 100mhz

max 1460mhz
[Nexus S Android Development] alen1901:
This is some bad score. I got score of 1750 on my galaxy 3 overclocked to 1200mhz...

Sent from my Nexus S
[Nexus S Android Development] alen1901:
Some info about new kernel? Is it better, whats battery..?

Sent from my Nexus S
[Nexus S Android Development] al_madd:
Oh yeah?? thats already 1000 different in score...:p:p:p

new kernel more smooth in my opinion..

battery life??have to wait for a few day to comment about battery life..
[Nexus S Android Development] xjerlzx:
i have issues with 17.5, when in deep idle for over the night.. connectivity is lost! any fix?
[Nexus S Android Development] DaXmax:
Bluetooth not working with CFS Cm9 ramdisk. Any1 cn confirm?
[Nexus S Android Development] caliban2:
Unbelievable, but v18 cfs is another step up regarding speed of the sys. :)

Had one funny fluke today, dunno if it's related to the kernel though (nothing else has changed and it never occurred before): imei-number was "unknown". Simple restart fixed it. Not that I was worried, I have a backup of my efs-folder (and I hope everyone else has too).

Update on the bootloop-bug:

It has transformed somehow. For some time now (17.5 & 18.0) the phone always boots up fine, but after some minutes of using it, it will first freeze and then reboot by itself. Sometimes I have to unlock simcard, sometimes not. After that it's stable for days, until I restart again.

Still no bad effects from it.

Another thing:

With v18 the scripts in init.d changed. The old ones are not deleted, did that manually. Do I see any change? Nope, v18 is fast either way. :cool:

Edit:

Mathkid, here's last_mesg. Says it's rebooting at the end and there's an oooops further up. Maybe it tells you something. pastebin.com/2fHM5hsR
[Nexus S Android Development] mixtapes08:
Maybe u did adjust ur int voltage. My imei gets unknown to when i adjust it.

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
Yeah its there but. It just clean one init.d script.

Sent from my Nexus S
[Nexus S Android Development] caliban2:
Nope, always the same voltages set by mk. I'd never post a bugreport when changing such important settings. Would be silly, wouldn't it? ^^

But good to know, maybe my phone can't take the kernel voltages on one cpu-speed and is always on the brink of crashing there... it happened one time now, I'll pass that bridge when I get there.
[Nexus S Android Development] italia0101:
What's the selective live oc do ?
[Nexus S Android Development] mixtapes08:
Yeah sorry :). I think ur phone can't handle uv. This kernel is int voltage undervolted by default btw.

Anyway MK did u flash the imosenyon.zip to enable swap capabilities? I want to try it but i need some feedback first from u or other users of this wonderful kernel. ;)

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
U can select a particular clockspeed range to live oc.

Ex.

U want to oc 100mhz to 400mhz by 110.

Now u will have a clockspeed of 110,220,440mhz. The rest will be on stock clockspeed.

Sent from my Nexus S
[Nexus S Android Development] italia0101:
Ah nice i like !
[Nexus S Android Development] alen1901:
Omg it's a MHZ, its a new antutu, score is up, i just quick looked bottom, sorry.

Sent from my Nexus S
[Nexus S Android Development] alen1901:
How to make normal volts, as UV DOESNT HELP BATTERY, IT ONLY MAKES PHONE UNSTABLE.

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Did someone piss in your Cheerios this morning? ;)
[Nexus S Android Development] caliban2:
yeah, i know my phone reacts a bit touchy when it comes to overclocking.

i have less problems with the cpu, but the gpu doesn't like it at all - no matter what voltages i set (need for speed at live-oc 110%? it will freeze...) absolutely no problems with the cpu on 1300 mhz with mathkid's voltages. 1400 appeared to be stable too, but i didn't push it. actually i'm more than happy with stock-speeds.

but as i said:

it just happened the one time since i got this phone. i consider it a hiccup. :)
[Nexus S Android Development] Nantaphan:
Ohh :) hurts haha

hey why i can't enable BT on 18 ram disk ver ? im on CyberGR
[Nexus S Android Development] caliban2:
pfff, it's not THAT good. :p

i'm getting 3387, but @ 1200 mhz and with a mail-sync during benchmark (i hate it if that happens).
[Nexus S Android Development] mixtapes08:
That is so sad. My phone can handle any oc even at 120 live oc or uv. Maybe im lucky hehehe

Sent from my Nexus S
[Nexus S Android Development] al_madd:
Ok..How about this??

same setting with airplane mode..:p:p:p

Edit..having error when listening to radio using tune in..

Max freq was 1460mhz..

Right now trying max freq 1300mhz with liveoc 105%.

Stock matr1x kernel...
[Nexus S Android Development] mixtapes08:
It actually helps mine. :) no reboots no freeze for me. Battery life averaging 22hrs a day medium to heavy use.

Sent from my Nexus S
[Nexus S Android Development] sperelli:
Same here, now even on standard version... my bt will nevermore work???
[Nexus S Android Development] nodstuff:
I disagree, if you can find the sweet spot with undervolting then it will save you battery, the only way it won't is if your set up is unstable and you get reboots.

A reboot will use more power than undervolting will save.

Once you get to know your phone you will find the sweet spot. Some can handle massive undervolting others can't handle any.

Undervolting is the reason this kernel has the best battery life.
[Nexus S Android Development] caliban2:
Nodstuff, you're half right.

Bedalus and others have proven that undervolting has almost no effect when it comes to arm voltages. Int-voltages have a higher effect.

Yet if it's stable, no harm done. But it's not the holy grail of batt-saving.
[Nexus S Android Development] dadaz007:
Same here with bluetooth.
[Nexus S Android Development] nodstuff:
Well if I'm half right then which part is wrong?

Anyone who has read bedalus's tread will tell you that the savings achieved from undervolting are negligible, 2% I believe it is, but they are savings none the less.

And as for INT values, that's what I was referring to.

We have both read the same material Caliban.

Matr1x is heavily undervolted in regards to INT values and that's why I was saying it was the best for battery life.

I find your "half right" opening statement to be quite pretentious.
[Nexus S Android Development] Pi3rluigi:
My imei changed to that "adorable" 00499....number!

I only flashed v18 CFS CM9 :mad:
[Nexus S Android Development] nodstuff:
Mine changed to that too when ics first came out for ns and it never caused me problems.

If you have a backup of your efs folder then you should be able to get your imei back.

Even if you can't you may not have any problems with the generic one.
[Nexus S Android Development] Pi3rluigi:
I backed up the efs folder,this is the second phone that got this problem for me,the first one I haven't the backup!

EDIT:the emei changed on Monday, when I flashed Black Infinitum Theme! I got the same message from WhatsApp now that I pushed the original efs folder,saying I can use the app in two different phone.

So not kernel flashing related
[Nexus S Android Development] B3rtbot:
@mathkid

Just out of general curiosity, why do your releases go up in .5's rather than whole numbers? :P
[Nexus S Android Development] SA-07:
any cm9 users pm me email id