yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Billchen0014:
OMG!!! Huge earthquake here in Melbourne Victoria, Australia, I was so scared!! Someone comfort me here on xda?? Right when Ausdroid was doing live podcasting.

oops! accidentally beamed from my awesome NEXUS S!
[Nexus S Android Development] apatal:
Heard it from relatives down there. Hope everyone's safe.

Sent from my Nexus S
[Nexus S Android Development] Billchen0014:
Wasn't too bad, the only thing collapsed was my spaghetti and marshmallow tower :D quite a jolt though. Should've left house first rather than tweeting about it.

oops! accidentally beamed from my awesome NEXUS S!
[Nexus S Android Development] apatal:
nahh. these days someone would tweet about being on fire before rolling to the ground to put it out. lol :D

Sent from my Nexus S
[Nexus S Android Development] Imppy:
You are halirous man lol
[Nexus S Android Development] lupoalberto12:
http://xdaforums.com/showthread.php?t=1371044

All ok?

Bye!

! :) !
[Nexus S Android Development] TigaTiger:
Its working for me. Maybe try and do a clean install? If it worked in the previous kernel, than its kernel related. If it didnt work at all on all the kernels, it could be rom. If your not sure when it stopped working. Than id try and test it with stock rom kernels.
[Nexus S Android Development] CrackerTeg:
That's definitely ROM related. My scripts load fine on slim, cybergr, apex, and codename. Xenon was one that they didn't work. Don't know why. Matr1x on all roms.
[Nexus S Android Development] SA-07:
So true :D
[Nexus S Android Development] caliban2:
way past full wipe, even tried skipping titanium backup for my apps and do a fresh install of them. didn't help. i know it's not working since matr1x v20.0, but if it works for you guys, it's cm9-related...

@mathkid:

gmail is crashing the system again. now this is kernel-related, because it worked fine for 3 days with v20. gonna complain via gtalk now... :p
[Nexus S Android Development] caleb1783:
even 21.5 kept hanging on me... especially when opening android xda app... :confused:

anyways, I restored to default volt and it seems to be runnin smooth...

I m using the settings on my signature...

I hope this isn't ur final version, but if it is. thank you... as u may know, I've been using ur kernel from day one... even tried ur matrix rom... lol

Sent via Divinus Nexus S...
[Nexus S Android Development] TigaTiger:
Okay.. What im running on is v7 CM9 (Kinda sucks that CM9, stopped/postponed v8), and v21.5.

Okay are you running CM9 nightlies or a stable build? If its nightlies, than that might be your problem.
[Nexus S Android Development] aLNG:
That happened to me also on v21.5
[Nexus S Android Development] caliban2:
looks like in my case it was obvious but i didn't want to see. :)

this morning i disabled fsync and it started crashing. re-enabled it and everything went back to normal after a reboot.

well, at least so far.

the "good" thing about all this:

mathkid got an earfull of complaints via gtalk, and boy - would you all like to know his very simple ways of bugfixing...!!! :D
[Nexus S Android Development] Paragon_X:
I'll just weigh in here with my exp using 21.5. Currently on aokp-39 and I use the amoled Nexus S. V20 was a dream for me but what I quickly notice is there is a slight speed increase with this model, not wait a second to draw up the homescreen etc. Battery seems on par but my major test will be when I leave for work (1hr full music with v20 usually drained only 10%)... i'll edit this later when I arrive at work and give an idea on the battery department, leaving my house with 100%
[Nexus S Android Development] RicardoOneri:
Every Mk kernels has undervolt if you are suffering some crash/freeze is because your device don't support them, put +25 on volt and you should be fine.

Also if someone whants to disable Fsync be carefull it can result in a bunch of crashes to alot off apps, if you see this flash kernel again to get back to deafult sethings.
[Nexus S Android Development] aLNG:
I used the same settings for v19.5, but never experienced something like that. Maybe because fsync is disabled.
[Nexus S Android Development] RicardoOneri:
Fsync are like Undervolt, so your device can't support both, leave it enable, kernel is super fast.
[Nexus S Android Development] raulillo88:
My phone has crashed three times today, with this apps: android email app, world newspapers and sincroguia tv

Enviado desde mi Nexus S usando Tapatalk 2
[Nexus S Android Development] mixtapes08:
Not kernel related. What you can do is boot in to cwm>advance>fix permissions>reboot

Sent from my Nexus S®
[Nexus S Android Development] raulillo88:
Ok I'll try it but not crash the app with a FC, crash the phone. The gyroscope works but not the keys. Al last always I have to remove the battery

Enviado desde mi Nexus S usando Tapatalk 2
[Nexus S Android Development] RicardoOneri:
Try to raise volt by +25 and try again
[Nexus S Android Development] caliban2:
And if you disabled fsync, enable it again.
[Nexus S Android Development] The1Shark:
Just got a freez..

I9023 cfs21.5, rooted stock rom with stock voltage, deep idle is off, 210-1365, smartass + noop.
[Nexus S Android Development] RicardoOneri:
Did you disable Fsync? If so leave it enable ...

Maiby you got to much overclock? If makes same thing on stock speed raise volt by +25.

Also read FAQ :)
[Nexus S Android Development] TechKidTarek:
cant wait to try this one out
[Nexus S Android Development] The1Shark:
I guess it is on since I didn't change the default. All other settings including voltage have not changed since version 20 which was the latest stable version on my phone.

I am using default rom voltage allready, do I need to raise the voltage 25 more?
[Nexus S Android Development] RicardoOneri:
Yes, this version (21.5) are undervolt and the undervolt on this version seems that only some can handle ( like me :p) , just raise +25 above default volt and you should be fine :)
[Nexus S Android Development] atl4ntis:
For every freq? Internal or arm?
[Nexus S Android Development] SA-07:
Just ARM will do... if reboots persist then do INT as well

Yes, for every freq
[Nexus S Android Development] The1Shark:
As I said I am already on stock voltage so I am 25+ already..

Anyhow I want to check my self. Can you please point me to rom default volt chart arm and int?

Thanks in advance
[Nexus S Android Development] RicardoOneri:
Download NSTolls form market : https://play.google.com/store/apps/details?id=mobi.cyann.nstools&hl=pt_PT

Click on Volt tab which is in the top bar (look screenshot)

If you whant to change voltages, unstick "Use configurations from kernel" and set ok, next click on for example 1000mhz and put +25 mv with the "+" simbol and click ok. Do this for all voltages

Done :)
[Nexus S Android Development] caliban2:
Stock voltages:

ARM

1000MHz @1250mV

800 MHz @1200

400 MHz @1050

200 MHz @950

100 MHz @950

INT

1000MHz @1100

800 MHz @1100

400 MHz @1100

200 MHz @1100

100 MHz @1000

You'll notice that arm isn't uv'ed that much, on some steps matr1x is even stock. It's int that is heavily scaled down.

And no, there are no stock-values for 1000+ MHz.
[Nexus S Android Development] raulillo88:
I've tried +25mv and still the same problem. Not freeze the phone but stop work the buttons and the touchscreen

Enviado desde mi Nexus S usando Tapatalk 2
[Nexus S Android Development] :
Did matr1x always work prefect for you? But v21.5 not working?

Can you

1) backup your current ROM

2) format system cache data

3) flash ROM

4) flash kernel

5) boot

...and see if the phone behaviour is correct?
[Nexus S Android Development] Po0yAn:
Tryingbevery new release and always revert back to v19.5 after a couple of days.

Seems the most stable for me.

NeXusS i9020T - Slim ICS V4.0 - Matr1x V19.5
[Nexus S Android Development] d_phekt:
Sounds similar to the issues I was having yesterday.. Do you have any tweaks installed?
[Nexus S Android Development] The1Shark:
Same problem here. Phone just freez buttons not responding. Sometimes last image is shown on the screen. Need to pull battery.

matr1x works like a charm on my phone up untill v20. V20 was the last stable version.

Rooted stock rom, +25 all freq ( rom voltage) 210-1365, smartass, noop, deep idle off.
[Nexus S Android Development] original21:
I always use dedalus way to flash roms. Never had a problem so far. It takes time but its safe.

As for for 21,5 i find it as stable and fast as 19,5.

I use NexusMV 14/06, smartassV2, min200 max1300.
[Nexus S Android Development] Sesese87:
Same issue here, on fresh install of slimICS.

ondemand 880-100, OC 110 (880-440), 440-200 screen off, deep idle on.

I will try with fsync enabled.
[Nexus S Android Development] micha3lvd:
Got same issue here..

Doesn't occur on 19.5

I just flashed cyberGR 14.0 and after full installation(clean install) and rebooted I flashed matr1x kernel. (used dalvik-wiper)

Used settings:

Ondemand 200/1000 Deadline

OC Target 400/800

DI = ON

No change with voltages
[Nexus S Android Development] The1Shark:
Fsync on my phone is kernel default ( which is "on" as I understand )

I am working on my voltage, I had ARM voltage raised but not INT so I am checking again.

the1shark
[Nexus S Android Development] raulillo88:
Always follow this steps. v21 crashes too but 20.5 I think not (I'm not sure because I use this version for a few hours and was released the v21)

Enviado desde mi Nexus S usando Tapatalk 2
[Nexus S Android Development] atl4ntis:
Same issue. 3 freeze , had to pull battery.

I9023 ics stock 4.0.4 smartassv2 noop.

Had freeze with +25 voltage aswell.

Edit: every kernel worked out flawless till 20.0 included.
[Nexus S Android Development] sdhanjal15:
No more complaints. Just go back to 19.5 or v 20. Don't even try the newer versions
[Nexus S Android Development] RicardoOneri:
Here is working flawless 21.5 for 3 days, with every multitask and heavy apps everyday....

Don't mess with stock voltages or sethings dont overclock if you have frezzes or reboots

If you got probles with everything stock put +25 on voltages
[Nexus S Android Development] micha3lvd:
What rom and device?
[Nexus S Android Development] RicardoOneri:
Was on ParanoidAndroid 1.3c but now I am on Kangyultra-EX 1.2 no problems on both.

Nexus S i9023 (SCLD)
[Nexus S Android Development] sdhanjal15:
Cyber gr mod

I recommend this very much
[Nexus S Android Development] apatal:
ok I'll give this a shot with the cfs version. I am actually on the bfs version with no problems after I got an SoD yesterday with cfs but I've been wondering why the latter is being weird with me when I used to have on my phone without issues. I will try your method. Maybe mixtapes does have a point about dirty flashing. I'll try and report back later. Thanks.
[Nexus S Android Development] sdhanjal15:
Everybody who loves MK for his work should show some love. Mk needs it. Thank this and see what we can do!
[Nexus S Android Development] d_phekt:
Agreed. He is very frustrated right now, which is understandable. He is only 16 and shouldn't have to worry about pleasing every single person. People tend to forget that this is a hobby, not his job. He has worked very hard and not everyone, but some people seem ungrateful. No wonder he is ready to move on.
[Nexus S Android Development] apatal:
+1 and DONE.

Donation made, mk! Just make sure you don't use it to buy SG3. :D

Just kidding. Do what you want with it. You deserve it.

Cheers! :)
[Nexus S Android Development] 4I-I:
Running v21.5 on remics 1.1 without any problems!

Mathkid = kernel-god!

Since the last few biulds my phone lasts for two days with moderate use!

Sent while eating an ice cream sandwich in the matr1x!

I flash roms therefore i am!!
[Nexus S Android Development] Harbb:
No one wants to hear complaints if you have overclocked or haven't set voltages back to stock. Not +25mV, stock volts for arm and int.

If you fulfill these requirements feel free to post details (detailed details even) and it will actually be looked at. Only a systematic approach will get things working for you.
[Nexus S Android Development] Sesese87:
ok, strange freezes stop now (I forgot to clear in my previous post that the phone will randomly freeze when opening the application xda).

Maybe it the sync off.. edit: ..or not, i agree that OC seems capricious with voltages usually stable.

I have an other problem now, my phone battery do not want to discharge and gives me an awesone autonomy.

Anyone report this issue?! :D

Great work MK!!
[Nexus S Android Development] The1Shark:
It is a very strange post.

No one is complaining ! I know MK works hard and I understand that he doesn't work for me and doesn't owe me a thing.

I am just trying to give my user experience. That is the main idea of this forum.

You can not expect that only those who doesn't have problems write here. I am sorry but you are completely missing the main idea of this forum.

I read on another post that MK is frustrated. He doesn't need to be ! Damn, He is smarter than many people I know..

On the metris, we were never told not to preform OC. Never told to return to the stock voltage.

The faq clearly says +25 to all freq in case of random reboots or freez.

Anyhow, I am using a diffrent voltage settings now and every thing works just fine. No reboot and no freezes.

Please note that voltage settings used on V20 with no problem probably not meet the requirements of kernels v20.5 - 21.5.

I9023, rooted stock, 210-1365, smartass, noop, deep idle is off.
[Nexus S Android Development] lupoalberto12:
i9023, ICS stock 4.0.4 (with Chainfire3D driver), v21.5 CFS, 200/1000 ondemand, deadline.

For me is ok.

Bye!

! :) !
[Nexus S Android Development] Harbb:
Forgive my slight bluntness before, it was well intentioned (as all my posts are). Maybe i should've thrown in an emoticon :rolleyes: Don't take it too seriously and it wasn't directed at anyone, it's just a general point. More general bluntness below also :p You've been warned.

This forum is not about User Experience, however - it is about developing. In a slightly more lenient time, each persons experience is wanted and accepted - this is great, such as when CPU Idle and Deep Idle were being contemplated on an otherwise rock solid kernel (not that i've had any problems recently anyway). However the last several pages worth are largely filled with people having problems with no indication of where the problem lies.

As such, if you reread my post, the most common problem/s should be eradicated before and then problems can actually be looked into. MK and the testers cannot fix UV or OC problems and i have my money on the fact that many people are suffering issues for this reason. 25mV tends to solve alot of UV problems, but when we are dealing with a relatively large amount of people this isn't accurate enough. The phone is built with stock voltages in mind, 100 - 1000MHz, so an issue with these settings indicates either hardware problems or kernel problems - otherwise it should simply be left to voltages dramas. I can't see mk releasing a normally volted kernel any time soon so this is pretty much a constant. If you have issues, make sure you still have them at stock values. No one wants a wild goose chase (well, geese are probably tasty.. :rolleyes:)

As always, feel free to OV/UC/JATO your phone. However issues that aren't on stock voltages don't really mean anything in the current context, and thus your issue is technically void. So if you come on here saying "calendar crashed, that plane crashed and my dog didn't walk itself" as your "User Experience", with no details and sketchy setup (thus a voided issue), you could right well classify it as a complaint.

Now.. back to Mythbusters :D
[Nexus S Android Development] leap_ahead:
hello guys ...i need your opinion ..i use matrix kernel 21.5 cfs with BLD BLN TOUCH WAKE DEEP IDLE all On .. deadline+on demand ..its ok ?
[Nexus S Android Development] caliban2:
Wait, so bug-reporting is considered complaining now? I can understand the rant against those who over clock, but you make it sound like everything apart from "great work" is bad. Not really, right?!
[Nexus S Android Development] Harbb:
Of course not. Unsure if you've read my most recent post above, however here is something to look over with regard to bug reports (the first result in google of "bug report" ;)). Nothing aimed at you (or anyone else), that's just pretty much a full essay of what i detailed in my last post.

Also, maybe you didn't read the second part of my other post:
[Nexus S Android Development] caliban2:
oh wow, thanks for the lecture, big cheese. i feel so much wiser now. if only i had known earlier. :p

btw, i have my own experience with bugreports and also how mk treats them. best thing was his suggestion how to solve the problems. :D (now mk is getting jumpy, hrhr)

back on topic:

looks like re-enabling fsync solved my sys-freezes. i had one more with gmail after enabling it, but then i cleared gmail-data and so far, so good (18 hours). maybe gmail's cache was still corrupted from the time it was disabled.
[Nexus S Android Development] Sesese87:
It's possible, but i feel obliged to clarify, for myself, that I had in the past dozens (hundreds?!:rolleyes:) of reboot because of the OC and/or UV, I have never reported on well. I think not being alone in this situation.

Here I think that's the nature of the freeze (when opening an application, no the usual reboot, BLD working again, voltages stables in almost all cases) which encouraged me to report, probably wrongly.

No, I'm not just a vulgar polluter of thread..or not.:D
[Nexus S Android Development] Harbb:
That's much better reporting in any sense, explaining why you reported it and possibly aiding in a resolution as a result. Cheers ;)
[Nexus S Android Development] Sesese87:
It seems that I still lack experience in the bug report useful (3 post for one issue..^^) :o
[Nexus S Android Development] The1Shark:
:thumbup:

I think it's an excellent idea.

Why don't we start from stock voltage and then implement any template that we want..
[Nexus S Android Development] caliban2:
Dude, this part is bull. It's common knowledge that overclocking can cause freezes, no matter on what device. If you oc and stuff starts to happen, this is always the first place to look at. After all you're running your device out of specs, kinda losing your guarantee. ^^ (please tell me at least you do know that oc'ing can also cause damage to your phone? Talking hardware here.)
[Nexus S Android Development] 4I-I:
bug-reporting is blasphemy! :O

haha jkng ;)
[Nexus S Android Development] dadaz007:
Wow, Thank you so much MK.

I stop using your kernel with v20 to try some others (because USB transfer speed pb on MY phone)

Trying v21.5 and wow great speed, smoothness...

Great battery life also.

Thanks again.
[Nexus S Android Development] caliban2:
Wait a sec, you mean I got an iPhone? :p
[Nexus S Android Development] LibertyMonger:
I never OC and always appreciate the work here and have shown my appreciation but when I flash a new kernel and it starts freezing when opening apps it is not normal so felt the need to agree with everyone else with the same issue and state that my phone is freezing up. No oc, all stock from the custom kernel. I never imagined it would blow up into so much drama, I wasn't complaining or dogging the work, thought I was helping. And besides, it is just a phone. So I just don't report anymore. I try to keep my 2 cents out of it, as I should have done with this post. But I am sure all the drama is keeping others from posting as well. Maybe my report wasn't perfect or professional but didn't seem I needed to explain much. Just flashed the kernel, tried using phone and it freezes and have to pull battery. That's all that happens. So I am back to 19.5. Never have this issue with it and I am fine with it. No big deal.
[Nexus S Android Development] Sesese87:
Again some random freeze here, i sent logcat

SlimICS 4.0 + deep-idle fix

Matrix 21.5 cfs ondemand-deadline

1000-100, live OC 100, deep idle on, 400-200 screen off

stock voltage (ARM/INT)

i9023
[Nexus S Android Development] caliban2:
@LibertyMonger:

if you follow the thread more closely, you'd notice i'm not the big cheese criticizing the quality of bugreports. ;) furthermore you'll also notice i was experiencing freezes as well, which were maybe caused by me disabling fsync on v21.5. re-enabling it seems to have fixed them, but i'm not so sure yet. i got them with 20.5 & 21.0 as well, no fsync-option there. i also set voltages to stock - is that it? but then, i never cared about voltages, yet earlier kernels were stable. no oc obviously, otherwise i wouldn't even be writing all this.

fact is:

something's changed after v20, and it's still causing troubles even for people who never oc'ed or did other fancy stuff. if it's still causing troubles for me has to be seen...

and before the big cheese falls in:

here are my kernel-settings. remove the ".txt"-extension, file goes to /data/data/mobi.cyann.nstools/settings, then load it in nstools. i'm too lazy to type all the details. ^^
[Nexus S Android Development] LibertyMonger:
I didn't quote you for that purpose bud, just going along with what you said, I do follow the thread closely. Sorry you took it the wrong way.
[Nexus S Android Development] The1Shark:
Well, I won't turn it into a fight but I am over clocking since day 1 with Matr1x kernel and never had any issues. My configuration has not been change since v16 and that is why I was supprised when freezes started.
[Nexus S Android Development] cøm3tx:
I'm using 21.5 now and... Wow this kernel is just great. Well done :-)
[Nexus S Android Development] TigaTiger:
Is it me or after i discharge my phone from any power supply (eg, wall, car) i get a 1-2% increase of battery life in the next few minutes?

This is the best kernel to be released as of now! for me. Awesome battery life, awesome smoothness and awesome everything.
[Nexus S Android Development] jlazkano:
Hello, I am new on kernel installing. I have CM9.0 on my Nexus S, I want to try the Matr1x kernel.

On the donwload page I have 2 files:

Matr1x-bfs_v21.5.zip

Matr1x-cfs_v21.5.zip

Which is the good one?

How must I install it? I have ClockworkMod Recovery v5.0.2.0

Thanks for all your help, best regards.
[Nexus S Android Development] alen1901:
v21.5 cfs. Just flash via recovery. If you bootloop, wipe cache and dalvik and restart. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] apatal:
Try the cfs version first since it's the safer choice. If you run into issues, then you can try the bfs version.

Sent from my Nexus S
[Nexus S Android Development] jayjay3333:
Is this still true for v21.5? I'm AMOLED (refer to signature) and have been using 20 bfs and it has been great. I used to use cfs until this post so tried it and it's great. Should I move to 21.5 bfs? cfs? stay on 20 because I'm AMOLED so it will have better battery saving results?

Thanks :D Awesome work MK and all those who helped him out! ;)
[Nexus S Android Development] SA-07:
v21.5 has PM_FAST and 56Hz for both AMOLED and SLCD :cool:
[Nexus S Android Development] jlazkano:
Thanks!

I got it:

Must configure the kernel? I see on some signatures something like this:

What is this?

Thanks and best regards.
[Nexus S Android Development] BuLLeT_PrOOf_wAlleTz:
Latest kernel Gave me slow 3g. On aokp 39. T-Mobile.. in r.I. switched back to stable version...wats up with that
[Nexus S Android Development] SA-07:
lol you sure that's a kernel issue? I'm on T-Mobile too and I don't have issues here.... what's up with that
[Nexus S Android Development] derekwilkinson:
(facepalm)
[Nexus S Android Development] caleb1783:
hmm.. is tgere something wrong w xda app? ever since version 20.0, when I try to open xda app. phone either slows down a lot, or hangs... only way out is battery pull...

I m using stock voltages w settings on my signature ...

Sent via Divinus Nexus S...
[Nexus S Android Development] damnmisur:
Had this happen with only select roms and when overclocked or not

Nexus stock voltages.

Sent from my Remics i9020a in the Matr1x