yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] SA-07:
Here is a proposition I am putting forward:

I am going to delete all the kernel zips after v20.0 and stop updating now

Let's pretend like anything after 20 never happened

What do you think?

I took "If it ain't broke then don't fix it" too far ;)
[Nexus S Android Development] caliban2:
I'm thinking "ohhh, now he's pouting"... :D

Okay, j/k. I'm thinking 21.5 ain't so bad, it offers great improvements on performance. And it really looks like fsync was the bugger, after I enabled it again it's fine. (You know the details from gtalk and my settings are in that file I uploaded.)

Problem is I didn't accumulate enough uptime yet to make a statement. It's been 18 hours after our talk yesterday and only 8 hours since I updated the rom today.

Edit:

Oh bite me, this can't be true. :mad:

Just after posting I opened a mail-notification, Gmail opened but empty and there I went again, pulling the battery. This phone is mocking me. ^^

Okay, so it has nothing to do with oc, voltages or fsync.
[Nexus S Android Development] CrackerTeg:
Sarcasm?

Personally, I think the current version is rock solid. The weird bug I had before with rebooting during a phone call seems to be gone and I can't be happier. Running stock kernel voltages overclocked to 1200, smartass v2, deadline scheduler. Oh yeah, slimICS is the ROM of choice. Those two together makes for a stupid quick, solid choice.
[Nexus S Android Development] caliban2:
Sarcasm? My last edit?

I wish it was...
[Nexus S Android Development] apatal:
have you been using the cfs version? I've been having issues with cfs as well, so after a number of tries, I gave up and used bfs and so far it's been treating my phone really well. also, if you're coming from a different kernel, you might like consider bedalus' suggestion of flashing clean with the rom, I.e. reboot to recovery, cache wipe and dalvik wipe (me I wiped everything except data), flashed rom then matr1x, then reboot. Hope this helps. :)

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
+1 the feezing problem bothers me a lot. I charge my phone up to 100 an hr ago and now my phone drains so badly because i pulled my battery 6 times in this very hr. Stock kernel config still causing freezing problem.

Sent from my Nexus S®
[Nexus S Android Development] polobunny:
I think that's what people meant when they said you were quick to react negatively to criticism. ;)

Either way, I think most freeze and glitches are due to undervolting. It's all fun to overclock and undervolt, till it freezes on you and then you jump in this thread crying.
[Nexus S Android Development] :
That's a tough call to make. What about a v22.0 with the .32 base and the new features like slub, fsync, etc...?
[Nexus S Android Development] mixtapes08:
Matrix ics is already been undervolted since day one...

Sent from my Nexus S®
[Nexus S Android Development] :
... Or build two .35 based, one with half the mods, the other with the remaining mods. We'll see which is stable. From there, split the mods again but only from the unstable set. Repeat and repeat halving each time until the culprit is discovered.
[Nexus S Android Development] The1Shark:
Which was never a problem prior to v20.5 ..
[Nexus S Android Development] apatal:
One thing I'm really happy about though is how this thread has remained one of the most active here in the NS forums. :)

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Ok I've decided to give one more push and work on this v22.0 to the fullest.

So revert to your last stable version while my testers and I get busy here :D

So just relax and enjoy!
[Nexus S Android Development] polobunny:
And so has been Trinity. Still caused it's lot of problems down the road though in the way the phone reacted to the voltage differences.

The voltage setting isn't completely impervious to the rest of the kernel, mind you. It's not something you can set on one kernel with certain settings and simply replicate on every other kernel, even so with the same kernel "line" but different revision. *shrugs*
[Nexus S Android Development] mixtapes08:
What im saying is that uv is not the problem why my phone freeze. My phone can handle any uv either matrix or tuv. So what are your opinions about that? The "undervolted" statement of your's is not the culprit i think...

Sent from my Nexus S®
[Nexus S Android Development] The1Shark:
I have a big smile on my face right now!

Thank you thank you thank you !
[Nexus S Android Development] Blackcrx:
thats a little extreme dont you think? haha

21.5 was freezing on my for a bit. but i reloaded the kernel, ran all stock voltages (arm and int) cleaned cache on apps that were freezing. been running fine so far.

i went back to 19.5 a couple of times cuz 21.5 kept crashing. but when 21.5 wasnt freezing i felt it preformed better than 19.5

keep up the good work man............. if you quit i want my donation back. haha
[Nexus S Android Development] polobunny:
So your phone is still not stable without any overclock and undervolt? :)
[Nexus S Android Development] mixtapes08:
Edit. Yup in the "latest" version.

I think you didn't even tried the kernel. Lol

Sent from my Nexus S®
[Nexus S Android Development] caliban2:
And neither was mine with 21.5. :)
[Nexus S Android Development] polobunny:
I think you're talking through your hat, though. I have tried nearly all Matr1x kernels, minus the very first ICS releases. ;)
[Nexus S Android Development] dinos3:
And i have reboot on 21.5 ;)

Waiting 22
[Nexus S Android Development] micha3lvd:
Have been running 21.5 now all day and it seems to be stable, no SoD or reboot.. however it doesn't seem to like soundhound (keeps crashing when I start the app..) so I just simply removed it xD

untill now: 10h, 6m on battery

screen on: 1u 48m

battery% : 55

settings: smartass v2 200/1000 deadline everything else kept stock
[Nexus S Android Development] Paragon_X:
Not sure if this is a kernel related issue but I thought I'd give it a shot. I notice if I reboot my battery stats either jump or shoot down for some odd reason. In this most recent case, I had it plugged in charging, rebooted and it went up 15%. And I can reboot and it drop equal amounts, any clues why?
[Nexus S Android Development] xjerlzx:
No issues with v21.5, fsync disabled.
[Nexus S Android Development] rasengan82:
Maybe a release with stock voltages would be awesome ;)
[Nexus S Android Development] The1Shark:
:thumbup:
[Nexus S Android Development] caliban2:
What for, you can always set stock voltages yourself. Also, voltages had nothing to do with the freezes. (Unless stock voltages suddenly became too low)
[Nexus S Android Development] CrackerTeg:
I meant MK's post prior to yours.
[Nexus S Android Development] Pipusz:
Maybe you could raise the voltages manually.
[Nexus S Android Development] Blackcrx:
OR.... you can open NStools and do it yourself

voltages supplied in the link below

http://xdaforums.com/showpost.php?p=27615910&postcount=5291

---------- Post added at 01:52 PM ---------- Previous post was at 01:51 PM ----------

i cant speak for everyone else. but after i set all stock voltages (arm and int) cleared cache for apps that locked up and crashed. i havent had any problems since
[Nexus S Android Development] caliban2:
I did the same - it just took more time to crash...
[Nexus S Android Development] Blackcrx:
haha. either i jinxed myself or you jinxed me. 21.5cfs with all stock voltages and cleared cache just crashed.

back to 19.5cfs until 22.0 gets released
[Nexus S Android Development] RicardoOneri:
21.5 cfs is running really stable on my device, no freezes or reboots in past 72h+ On.

Also will help Mk with the 22.0 (test) ... hope this one will rock even more for everyone :D
[Nexus S Android Development] migueldbr:
21.5 cfs...awesome kernel. running flawlessly on my i9023
[Nexus S Android Development] SA-07:
Hmm.. looks like some people are running 21.5 well while others are not... don't worry v22.0 will be much better
[Nexus S Android Development] apatal:
I don't know what I did right (or wrong) but my phone is running bfs without issue so far (had crashes with cfs too before this, so my phone is not special). just tried bedalus suggestion, and did this:

(1) format cache

(2) format system

(3) format boot

(4) do not format data and sdcard

(5) wipe dalvik cache

(6) wipe battery stats (optional)

(7) flash ROM (rascream)

(8) flash kernel (v21.5 bfs)

(9) fixed permissions

(10) reboot

after that you can install busybox or whatever scripts or tweaks you need and reboot one more time. works fine for me so far. I'll edit this post if ever I do encounter any issues later on.

Cheers! :D
[Nexus S Android Development] BuLLeT_PrOOf_wAlleTz:
Iono but flashed previous version.. and everything is back to normal...
[Nexus S Android Development] vis80k:
never fixed permission while switching roms...

what does step #9 from above mean? does it mean to make sure all files are given proper permissions?!
[Nexus S Android Development] apatal:
I'll be honest. I don't exactly know what it does, but rascarlo always recommends it when flashing his roms. :D

and yeah, I had an issue once with some apps after flashing a new from, such as the Google music player crashing, which was fixed after I fixed permissions in recovery. :)

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
Edit. Nvm

Sent from my Nexus S®
[Nexus S Android Development] cdljl2005:
the same! on my tricky ns (I believe it IS different from others, I experience all kinds of weird bugs while my friends with same ROM/kernel don't...:() 19.5 runs best.
[Nexus S Android Development] apatal:
OK PEOPLE LISTEN UP.

The development of version 22 has now gone beyond state borders and is now a full-blown international effort between MK and a bunch of testers from different walks of life and different parts of the globe. MK is hard at work late in the night in order to bring you guys the good stuff ASAP so let's all try and help out by being more patient and refraining from posting "bug reports" (read: unsolicited complaints) in the thread for the meantime. Instead, let's all join together in giving the much needed moral support to one the best developers for the NS at the moment: MK.

I know you guys love his work so I'll be expecting tons of supporting posts here. I'll be happy to answer any questions you may feel you need answered immediately but for the more technical stuffs, I'll have to defer to MK and all the other guys here who is way smarter than me. Hope this ends the unnecessary troll-ish behavior for now. Cheers, people! :D
[Nexus S Android Development] Pi3rluigi:
Very good battery life and stability, for now this what I got from first cimplete recharge

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] Blackcrx:
Respect!

I'm willing to help as a tester if needed.
[Nexus S Android Development] caliban2:
Yeah, but those tests may take a while. :) mk told me latest test version already crashed for 2 people, my phone is getting to 10 hours uptime with it. ^^
[Nexus S Android Development] tonylee83:
Sry mat it is working with ma laptop. But smhow not working with the phone.

Ty
[Nexus S Android Development] jalyn02:
Do this kernel change the boot animation?
[Nexus S Android Development] SA-07:
Nope!
[Nexus S Android Development] jalyn02:
Thanks. One last thing, what's the difference between CSF and BFS? I have a T-Mobile Nexus S and one of your links are down. Can I just flash the one that's up?
[Nexus S Android Development] SA-07:
Check my FAQ ;)
[Nexus S Android Development] jalyn02:
Thanks.
[Nexus S Android Development] aic719:
Bah where's v13! I'm addicted to this thing! I end up checking every hour of a minimum! :P

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] aic719:
How do you know :O

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] defia:
my first time using matr1x, so far the stock ics with the bfs version 12.5 is very smooth and fast, i think it the best kernel i've used

but when i run quadrant, it hangs on cpu test(h.264), manully kill quadrant and then run again, it hangs on the very begining of cpu test unless i clean the app data of quadrant

edit:there is no settings in voodoo controller app
[Nexus S Android Development] KBanause:
The latest version of quadrant is now nearly one year old (according to the market. I don't know about the paid version, I can't find it in the market). It looks like the developers stopped working on it.

Anyways, it needs an update for ICS and the 3.0.x kernel versions...

Greetings,

KBanause
[Nexus S Android Development] TrueYears:
what are some google voltages settings for this kernel?
[Nexus S Android Development] defia:
thx

how can i set voodoo option? my voodoo control app says the device doesn't run a kernal supporting extended sound controls
[Nexus S Android Development] TrueYears:
Yeah same here!
[Nexus S Android Development] DaX05:
Just had 2 reboots back to back. Wasn't near my laptop to provide a logcat. Was on Youtube when it happened.

Beamed from my Nexus S
[Nexus S Android Development] KBanause:
Funny. I have had the same. But after during the second reboot the phone froze in the bootanimation. I had to pull the battery. Same happened the next two reboots until it finally rebooted without problems...
[Nexus S Android Development] aic719:
Hmph

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] Neuron:
is bln working on 12.5?
[Nexus S Android Development] KBanause:
yes, yes it is working.

NSTools is the hint...
[Nexus S Android Development] Tarun.krthkr:
voodoo is not working for me!!

i installed *Matr1x* with BLN and voodoo v12.5 ics...everything is working fine but voodoo is not working for...the voodoo control 2.1.1 app which i downloaded from market shows..."sorry,this device doesn't run a kernel supporting extended sound controls"...help...:o
[Nexus S Android Development] falconrulz:
Voodoo is not yet 'put' in the kernel I guess
[Nexus S Android Development] stewarta:
+1. I really do think that as with ROMs, it comes down to how one installs. I don't have issues when I boot into Recovery (not via Rom Manager), I wipe the cache and then flash Dalvik-Wiper. While SmartassV2 and Noop give good battery usage, I think that one of these is flakey. Of course, as with everything we do with Android development/hacking, we will all have different views. C'est la vie!
[Nexus S Android Development] caliban2:
Long time since I last played with scheduler, but noop was always buggy for me. Didn't matter if with glados, matr1x, stock-rom, cm9, lazy or smartassv2.
[Nexus S Android Development] bradtn:
Does anyone have zip to to flash default CPU settings for nexus s? just incase situation gets sticky . Couldnt find anything. Thanks a ton
[Nexus S Android Development] xjerlzx:
U coupled noop with?
[Nexus S Android Development] :
Using nstools? Find the thread in apps/themes section, there is a reset zip in the op
[Nexus S Android Development] micha3lvd:
Just disable restore settings on boot in last tab and reboot :)
[Nexus S Android Development] caliban2:
I mentioned that, didn't I? Second sentence... :)
[Nexus S Android Development] xjerlzx:
I mean with what governor
[Nexus S Android Development] bradtn:
do you mean just uncheck set on boot?
[Nexus S Android Development] caliban2:
Lazy and smartassv2
[Nexus S Android Development] lupoalberto12:
Stick it on the first post but I would add:

0) Make a Nandroid Backup :rolleyes: !

8b) Flash "Superuser" (if you use stock rom).

Which is the configuration of the other testers?

My is i9023, ICS stock 4.0.4 (with Chainfire3D driver), v21.5 CFS, 200/1000 ondemand, deadline.

So we know on which devices is tested.

Bye!

! :) !
[Nexus S Android Development] micha3lvd:
Yeah, after reboot it restores settings to default.
[Nexus S Android Development] caliban2:
Let's wait until mathkid wakes up, asked him to create a private group for beta testers. No need to clutter the official thread with this stuff!
[Nexus S Android Development] Billchen0014:
Count me in!

oops! accidentally beamed from my awesome NEXUS S!
[Nexus S Android Development] migueldbr:
allow me to correct this...lol. Not running flawlessly. Had two freezes(completely frozed phone, had to remove the battery). Its kernel related because i haven't had any freeze using slim's modified kernel for a long time=/
[Nexus S Android Development] TigaTiger:
You MUST atleast boot ONCE before you flash the kernel. Formatting SD card is optional if you want to clean out some rubbish and start from scratch. You wipe battery stats if you have problems with your battery readings, change to another battery or calibrate your battery.

1) format /system /data /cache /boot

2) wipe dalvik cache

3) flash rom and gapps

4) Boot up for the first time and it should work

5) Optional: Only do this after you booted up once. Flash the kernel.
[Nexus S Android Development] caliban2:
i never had any problems with flashing rom + gapps + kernel in one go.

so i guess it's nice to do, but far from being a "MUST"... :)
[Nexus S Android Development] apatal:
actually, he's using 21.5 so it's not exactly beta testing in the strictest sense...and mk has chosen his testers, which includes bedalus, so the kernel is in good hands. ;)

let's wait for their official update. all I can say is that mk is going back to basics and is focused on isolating the offending mods so let's all wish him all the best. and guys, enough with the freezing reports please. mk has acknowledged the problem and is promising a better, more stable release in the very near future.

Cheers! :)

Sent from my Nexus S
[Nexus S Android Development] apatal:
It's two school of thoughts that I never have been able to resolve. Maybe he has a reason why he feels a reboot is needed for the rom before flashing a custom kernel. Mind sharing that reason? :)

Sent from my Nexus S
[Nexus S Android Development] caliban2:
Beats me, basically kernel zip includes boot.img, zimage and some modules. Those overwrite their stock-counterparts. Clean and smooth. Dunno what good a boot with stock-kernel should do...?

Edit:

To all the beta-testers, whoever you may be: :)

Next time it freezes, try to pull a log via adb. During the last freeze I noticed that the phone appeared completely dead, but was fully accessible with adb. (.35-test finally froze for me as well after 15:30 hrs ^^)
[Nexus S Android Development] mixtapes08:
Deleted... :-)
[Nexus S Android Development] EleventhHour2139:
As soon as you soft brick doing it, well I'd say that's a good enough reason. If it hasn't happened to you, congrats. Never had a soft brick doing a reboot between rom/kernel flashes, but had several attempting to do them both with no reboots in between.

No idea why this is, but it's worth a few minutes extra I feel.
[Nexus S Android Development] :
For a while I flashed every new version of every kernel over a clean install of slim ics (i think it was around about v2.0) without an interim boot/reboot, and never had a problem. Later I flashed pretty much every version of every ROM with T132-I, again with no interim boot/reboot, and never had a problem. If any new members want to check out the results, follow my signature.
[Nexus S Android Development] polobunny:
You're absolutely crazy. I always do the rain dance after every flash, format all my SD contents and sacrifice a lamb when I get a freeze/reboot. That's just how I roll. :p
[Nexus S Android Development] sdhanjal15:
This is pretty awesome!
[Nexus S Android Development] qtwrk:
has anyone else experienced what i have experienced in both 21.5 BFS and 21.5 CFS

the sleep of death i think , my phone was USB-charging with my laptop , when i try to use and press power button several times and it doesn't light up. this happened few times when or when not charging.

playing music with screen-off , jammed and automatically reboots.

AOKP B39 deadlinea, smartassv2 , deep idle on , i supposed i should turn deep idle off ?

and i did have same problem back 20.0 and 20.5 even 21.0 ... :crying:
[Nexus S Android Development] RicardoOneri:
Did you read the post above? Please wait we are working on it, Mk alleady know there is problems and are hard working to fix it like testers are helping him.
[Nexus S Android Development] jayjay3333:
I decided to give 21.5 a go. Been using bfs v20 for some time now. Chose bfs V21.5 and been running it since noon. One small freeze up with Gmail and weird dark screen after a metamorph app reboot...but other than that smooth! Maybe my Nexus is unique but I have always had very few issues on Matr1x and have been using for a while. Cfs and bfs V20 have proven to be efficient battery savers for me. Mostly on Smartassv2 and probably equally between deadline and noop...but more noop as of the last 2 weeks or so. Since my phone handles Matrix so well I can't wait for 22! Been on CM9 nightlies for a while now also. Currently latest...0621.
[Nexus S Android Development] apatal:
good for you! your phone is really one of a kind. keep your eyes peeled for the next update, that one will really be a winner. :)
[Nexus S Android Development] 309041291a:
I still feel like I'm in a gloating position with my v20 setup. Scoring over 5 hours on-screen use in over 24 hours for the win! Thank you MK :)
[Nexus S Android Development] sdhanjal15:
Bro I'm still winning. Those two spikes of charging was me transferring a 2 gb file and lot of music. But hey this is my daily use.
[Nexus S Android Development] Imppy:
What settings are you using?
[Nexus S Android Development] sdhanjal15:
Go back a couple of pages
[Nexus S Android Development] 309041291a:
Try using 3G/HSPA+ instead of 2G/WiFi and get off of the red battery saving theme :). On right, and try to to do it in like 27 hours or more :3. Then we shall see who is winning! Challenge accepted?
[Nexus S Android Development] sdhanjal15:
Don't have 3g in my area and I took it off of my plan because it was useless to me. ...I have blazing have fast wifi and I'm home a lot. So yeahhhhbbh
[Nexus S Android Development] 309041291a:
Check my signature (or thread "5 hours + screen use", i think it was called). I'm trying out Paranoid Android ROM right now, but i was on Gummy.

3G and HSPA+ use more power than 2G and WiFi, you have a black and red theme (those are made for battery saving on AMOLED screens), and my 2G connection sucks lol. So I won't be using it.
[Nexus S Android Development] sdhanjal15:
I can't get rid of this theme. Its my rom
[Nexus S Android Development] 309041291a:
What ROM? Hm, to level the playing field I'm going to switch to a Red Theme....
[Nexus S Android Development] sdhanjal15:
Joking...but I'm using cybergrmod. And using the cm9 red theme from the play store. Just saying....this thread to discuss this. Sorry mk
[Nexus S Android Development] 4I-I:
Why dont yoh start your own thread? "Battery+screen on time competition" or sth? xD

I actually read through all the off topic posts because i wanted to stay up to date with matr1x! Pls stop spaming this thread! ;)

Sent while eating an ice cream sandwich in the matr1x!

I flash roms therefore i am!!
[Nexus S Android Development] qtwrk:
I am Sorry, I didn't mean to be rude , but there are hundreds pages back there......... I didn't mean any disrespect, just reading lots lots English text is making me crazy... :o
[Nexus S Android Development] apatal:
that's alright. be rest assured, mk and his testers is on top of the situation so you guys can have a better update soon. in the meantime, feel free to revert to v19.5 since it's the last stable version. :)

Sent from my Nexus S
[Nexus S Android Development] 309041291a:
I'm actually trying to find a good Red theme. Can you point me in the direction of a few? I have a red keyboard I can publically post the link here for you and other users.

And yeah, sorry MK :/. We shall stop if you so wish. *Bows* kidding :P. But if it really is a problem we can PM instead of this :)
[Nexus S Android Development] sperelli:
Still 19.5 wins the competition for power save compared to 21.5, in my case.