yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] nosfaratu:
the battery lasted me for two days, and now with this rom not.

I'll try that and then tell the result.

thank you
[Nexus S Android Development] mike216:
60 is perfect! Been running since the day it was released and it has been nothing short of amazing! Maybe you should try a great kernel like matrix, franco's or glados before you say some dumb ****

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
With matrix I probably could go 40 hours with moderate use if I pushed it. If you guys did a full wipe and are still having problems then try a different kernel

This rom has more options much better ram management than previous versions its just simply the best

Just came back from ICS with a nandroid restore and I know I most likely wont be on ICS for a while because this build is that good!

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
Yes warn and fuzzy when I see 50% left on battery with 20 hours of use so learn how to read you dumb ****

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
I am joking!

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] saranyan:
Check in the op. In the link provided theme Chooser is available as a separate download. Just flash that in recovery.
[Nexus S Android Development] LibertyMonger:
Huh... My last post went missing lol. Don't know why. Anyway I have another question, I am having a hard time finding a sure answer for it's about flashing a different radio. I have read a bunch throughout the radio thread and can't find any sure answers, I have asked in that thread and just got ignored lol. I live in Cincinnati, Oh and have CBW wireless, was wondering if it is a good idea to flash a different Radio on this ROM and Matr1x kernel and if so can someone suggest one? It would be a big help and much appreciated! Thanks for any help...
[Nexus S Android Development] uansari1:
Who dey! Lol.. CBW piggyback on T-mobile, so use whatever radio the T-mo guys recommend.. As for kernel, either matrix, franco, or glados should be fine..ultimately it depends on which works best on your phone.
[Nexus S Android Development] cookiecaper:
Been waiting for changelog to upgrade. Any ETA on that?
[Nexus S Android Development] jark99:
Me and you both lol
[Nexus S Android Development] Zisi911:
im waiting for the changelog too. does anybody know if nscollab will get android 4.0 ???
[Nexus S Android Development] al_madd:
anyone get problem the phone does not want to enter sleep??

When I press power button, after a few seconds the phone wake again...press again, wake again..weird...

latest ns collab,matr1x 11.5 cfs, live oc 110, go launcher,ondemand
[Nexus S Android Development] LibertyMonger:
Can't open CPU in NSTools. Anybody have an idea why? Using Matr1x 11.5
[Nexus S Android Development] SA-07:
What does it say when you try to open it?
[Nexus S Android Development] LibertyMonger:
NSTools flashed an error earlier today but It was too fast for me to read it, I read enough of it when it flashed that I seen it say something about the Kernel. And now NSTools forcecloses when I try to open CPU.
[Nexus S Android Development] SA-07:
what about setcpu?
[Nexus S Android Development] LibertyMonger:
Setcpu forcecloses when I open voltages...
[Nexus S Android Development] SA-07:
Why are you getting these stupid issues??

Both nstools and setcpu work fine for me.

For now, can you restore a nandroid of another rom and flash v11.5 and see if the problem still exists?
[Nexus S Android Development] LibertyMonger:
Actually it's not the first time i have had this issue, I have had it with your previous kernels on stock GB as well. Seems to happen after a few days of use. I will flash something else and report back tomorrow. I'm not doing anything much different, only clocked at 1000mhz and liveoc 100 and default voltages. Everything is running great, no other issues I just wanted to open CPU in NSTools lol.

***EDIT

OOPS Spoke too soon, now my phone is froze at the lockscreen, can't do anything except pull battery I guess...DArn everything always seems great for about a week then it starts bugging
[Nexus S Android Development] mike216:
This usually happens when nstools holds on to previous settings from a previous kernel go to themes and apps section and look for the nstools thread and download nstools rest zip and flash that before flashing any kernel I've had the exact same thing happen to me a couple times

Linux The Peoples OS
[Nexus S Android Development] Ok_Kaleidoscope5109:
did you do a full wipe? this is perhaps the most important part. do a full wipe and then install NSTools and then SetCPU. It should work.
[Nexus S Android Development] LibertyMonger:
I did a full wipe before flashing NSCollab, and I reset the kernel once but not sure if I did it after flashing NSCollab and reflashing the Kernel. I will try to reset the kernel and reflashing it, that makes alot of sense thanks guys!
[Nexus S Android Development] Ok_Kaleidoscope5109:
Reflash THEN flash a kernel of choice (i.e. Matr1x) because flashing NSCollab will install its default kernel (CM7)
[Nexus S Android Development] SA-07:
Don't forget to wipe dalvik cache
[Nexus S Android Development] Ok_Kaleidoscope5109:
doesn't a wipe all in CWM wipe everything anyway?

dalvik is stored in /data right?
[Nexus S Android Development] benrees21:
Had that issue last night with NSTools. Power off and boot into recovery and flash the kernel again. Then boot up and it should be OK. You will have to do the settings again.

Sent from my Nexus S on CM9, Morfic's SEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] al_madd:
Anyone having issue with mount sd card???

NVM...Solved!!!
[Nexus S Android Development] Ok_Kaleidoscope5109:
ROM still feels sluggish. Got a bootloop today. I'm moving to MV for a test run. 60 is definitely NOT a good release (compared to 50)
[Nexus S Android Development] got2best:
Report back what u find u am curious :)
[Nexus S Android Development] al_madd:
For me...latest release is very good...at first have a problem about mount sd card...now it fixed...

smooth,not random reboots,long battery life...I love it..:D:D
[Nexus S Android Development] Ok_Kaleidoscope5109:
Well I get a reboot on 60 every once in a while. I got my first reboot on MV. However, it's FAST. I don't feel any slowdown. I'm not sure if its because the minfree settings are tweaked, but Frank's settings have been used since .42 or something.

I just don't know what made 60 slower than 50.
[Nexus S Android Development] thegtfusion:
where can I find the theme chooser?
[Nexus S Android Development] Burbruee:
Went back to this after two weeks of ics. IT'S SO FAST AND SMOOTH IN COMPARISON! :eek:
[Nexus S Android Development] bkanuka:
I'm really considering coming back here. Ics just doesn't have the maturity.
[Nexus S Android Development] jark99:
Changelog request. :)
[Nexus S Android Development] LibertyMonger:
Absolutely no sluggishness and zero bootloops everything has been great no reason for me to even consider a different ROM til official ICS.
[Nexus S Android Development] thegtfusion:
Yea.. i wonder why people complain about sluggishness and ****. Flashed it today with the franco 25 nov kernel, i have never got such good battery life. I have no bootloops, not even one reboot. Its by far the best release of nscollab for me. Its superfast. :D. I use it with the cm7 ics theme. Im gonna stay on this rom till official ICS ota comes out :P :D
[Nexus S Android Development] LibertyMonger:
Well I always speak to soon and stick my foot right in my mouth lol. Not too big a deal but decided to try and overclock with NSTools running the Matr1x 11.5 kernel and it automatically reboots, now my phone is unstable. All was fine at 1000mhz for about a week. Also when I was on stock 2.3.6 with the Matr1x kernel I could overclock to 1400mhz and be mostly stable and superfast. But everything always seems fine for about a week then problems start occurring.

***I had to use the NSTools reset and hoping it is ok for now, would like to overclock to 1200mhz is there something I am missing or is this the case with others using NSCollab as well?
[Nexus S Android Development] akshayf:
Can you please tell which ics theme are you using.... ?

Thanks......
[Nexus S Android Development] LibertyMonger:
***I am sorry for this post and deepfully regret it, I got upset so please forgive me***

HEY MATHKID what the heck is this private message about? Are you freakin serious???

"Dude if matrix can't run on ur phone then whatever, switch kernels haha

I'd rather see you have good experiences with another kernel rather than complain about mine"- mathkid95

I am not complaining, I am simply reporting my experience with this ROM and your Kernel if you can't handle that then you need to quit sharing. I actually complimented your kernel just now and didn't even post in your thread. I really don't appreciate the private "kid" like message. UNBELIEVABLE! Is this even permitted? WOW dude you got issues!

How the heck would I ever even know if my phone is the reason I can't overclock now without asking about the issue? I still can't believe the private message it has got me pretty P.O'd. Sorry guys I had to vent lol.
[Nexus S Android Development] SA-07:
What the heck man? I'm not accusing you of complaining, and I'm not doing anything wrong. I basically meant, we have tried everything we could to get this kernel working for you and nothing seemed to have worked since you keep experiencing problems. So since nothing has worked, try out another kernel and see if you get issues. Maybe I might have come off as rude, so I agree and I apologize. No need to go all berserk, just a little misunderstanding ;)
[Nexus S Android Development] bkanuka:
Umm not that this needs to be said, because it should be obvious to anyone who reads your post, but mathkid's message seems mature, honest, and completely normal - if not better than normal from a developer.

You've done a number of seriously offensive an immature things by posting your message:

You reposted a private message in a public forum. This is wrong by most ethical standards.

You used "kid" in a derogatory fashion in a community which is largely run by adults. This deters very talented young people from joining software development because they feel intimidated. And not that it should matter but in case you are unaware mathkid IS 16 which is a kid by many standards. I seriously respect his talent from someone his age.

You also asked someone to stop sharing something that he's done completely in his own time. And for free. It took begging from the community for math kid to finally accept donations. There is no social context in which asking someone to stop sharing his art is the right thing to do.

********

EDIT: okay so i guess all is settled. Good on you liberty for apologizing and then not deleting your post. People make mistakes.

I'm sure i came across as a douche too. I just wanted to make sure my message was heard. But all said and done, I'm just glad there's no fighting. Lets keep it that way :-)
[Nexus S Android Development] SA-07:
Yeah it was just a misunderstanding, I didn't mean to accuse anybody of anything... Ok no more fighting :D
[Nexus S Android Development] LibertyMonger:
We figured out my last issue and solved it. It wasn't a big deal. I am posting again with another issue simply to see if I can solve it as well. I am not gonna flash from kernel to kernel every time I have an issue, I would rather solve the issue it seems to make more sense.

What I was trying to say is today was the first time I tried to overclock running NSCollab and I got automatic sod and reboot. When I was on stock and Matr1x I was able to overclock, I ran my phone at 1300mhz for about 2 weeks.

Other than that Matr1x and NSCollab has been great, I would like to see it work, if not I will have to try something else. So far it's been working I can do without the overclock.
[Nexus S Android Development] SA-07:
Ok, I have had great success on NSCollab with oc, so it has to be either a voltage or deep idle problem.

try disabling deep idle using nstools then bump up all the voltages by 20 as a start off point...

try that and lemme know!
[Nexus S Android Development] LibertyMonger:
I am very sorry Mk, I took it the wrong way cause I felt pretty offended. I know your message sounds reasonable but I felt that I haven't had many issues and love your kernel and just want it to work. And thank you for not getting as upset as I did, I should have handled it a different way, I just didn't think a private message was appropriate.

***And it is amazing you are only 16 and makes me feel even more stupid and immature lol. Sorry again buddy I deepfully regret it man.

***You have been a major help for me and I greatly appreciate it I guess that is why, I didn't expect an answer like that. I am still learning so the issues are my fault.

***Actually I should have learned by now to make the adjustments and it would have prevented my post, but I appreciate any advice as I am not sure of everything yet, I need to start doing these things on my own. So again, you are right mathkid.
[Nexus S Android Development] Jibreil:
The ROM and neither the baseband or kernel has anything to do with the SIM.

Your SIM is probably damaged, or coincidentally expired, you need to get it replaced with the newest 64-bit or if any higher one available with your service provider.
[Nexus S Android Development] huynhc:
Thanks just went to go pick one up. Works like a charm. I didn't think the rom and kernal had anything to do with the sim card but had to ask to see if anyone else had the issue given the timing of the flash. Phone works again so I'm happy. Sorry for my ignorance but I'm coming from a cdma world.... thanks again for the help!
[Nexus S Android Development] frank707:
[03/21] NSCollab 1.0.12

[system] CM 7 Nightly #28

[update] gapps-gb-20110307

[update] Busybox 1.19.0

[theme] Notification Bar Power Toggles [ClassicalGas]

[theme] Dark-Launcher2.apk [Jonathon Grigg]

ROM Download: NSCollab-1.0.12

[First installation of NSCollab ROM] - Wipe Data/Cache Required

[Updating from NSCollab 1.0.XX] - NO Wipe Required

[MD5 : 60443be4db4a0e40d90ecd8b1f8a7c34 ]
[Nexus S Android Development] :
thanks alot. :) also we missed voodo v6 for now.

am i so fast ? link says 1.0.11? :)

Fixed thanks.
[Nexus S Android Development] frank707:
Would like to know if Rom Manager Premium users are receiving NSCollab update notifications?
[Nexus S Android Development] :
From here in turkey we can't reach market for paid softwares so i dont have and i dont want to use applanet for it
[Nexus S Android Development] bumer17:
Hi, how do I apply dark launcher?
[Nexus S Android Development] :
@frank707 Thanks pretty fine :)

@Jonathon Grigg Thanks for the launcher :)
[Nexus S Android Development] Jonathon Grigg:
It should be applied automatically when flashing 1.0.12, you may need to check your on 1.0.12 :p

Sent from my Nexus S
[Nexus S Android Development] heroheto:
Works for me

NSCollab 1.0.12 with Netarchy 1.3.0 cfs @ 1.2
[Nexus S Android Development] eiabea:
great rom :)

just waiting for BLN :)
[Nexus S Android Development] JmPTaz09:
Rom Manager Premium with update notifications on, did not receive any type of notification that this was available; had to hit "download now" and manually check for it to download.
[Nexus S Android Development] kevin_ngckk:
I dont want the black notice bar. How can i change it back?? And is it possible to use the stock launcher with a 5 dock bar???
[Nexus S Android Development] suhas_sm:
Whats BLN ? :)

How do I over clock my nexus S ? Should I be fiddling SetCPU ? I feel like using it :)
[Nexus S Android Development] :
(B)ack (L)ight (N)otification
[Nexus S Android Development] buachaille:
Yep, working for me
[Nexus S Android Development] lfmmoura:
I was on 10.0.10 and upgraded to 10.0.12. So far, everything is smooth. The widgets on the status bar finally look great! :)

Before trying NSCollab, I tried a few CM7 nightlies (even the ones that were recommended by several as being stable) and everything was quite glitchy. NSCollab seems much faster and more stable. Can't imagine myself going back to stock ever again!

Kudos to the developers! :)
[Nexus S Android Development] dmenge:
Is the battery life just as good as the CM7 Nightlies?

Greets
[Nexus S Android Development] Alexkidd85:
Quote :D

Pleaaaaase give us BLN!!!:D
[Nexus S Android Development] serrov91:
Yeah right! BLN all the way! Netarchy's gonna update his kernel to support BLN when it is in a final release.. After that, mister frank could use it in NSCollab mod ROM! Can't wait!
[Nexus S Android Development] SA-07:
Yeah, it's no big deal :)
[Nexus S Android Development] benrees21:
Mathkid is mad skilled for 16! Do an ICS ROM!! Lol.

Sent from my Nexus S on CM9, Morfic's SEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] LibertyMonger:
***Actually I should have learned by now to make the adjustments on my own and tried them before asking for help and it would have prevented my post, but I appreciate any advice as I am not sure of everything yet, I need to start doing these things on my own. So again, you are right mathkid and thanks Buddy
[Nexus S Android Development] SA-07:
Yeah its pretty easy once you get the hang of it haha
[Nexus S Android Development] SA-07:
Hehehehe ;)
[Nexus S Android Development] benrees21:
Don't be scared to ask for help, just try and do some stuff on your own first and if you have no luck then ask. I've got plenty of funny messages from MK!

Sent from my Nexus S on CM9, Morfic's SEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] LibertyMonger:
Actually I think I would have taken it better if Mk would have just posted here that I am stupid and told me to learn how to manage the kernel rather than the private message telling me to get away from his kernel lmao! I would have realized it was my fault. I actually didn't think of making adjustments since the default settings have been working so good. So maybe next time Mk tell the noob to learn how to manage the kernel lol.
[Nexus S Android Development] SA-07:
Haha will do!
[Nexus S Android Development] thegtfusion:
The one from market frkm sonny sekhon.
[Nexus S Android Development] djjonastybe:
why dont you use cm7.1.0.1 as a base?

Does this rom have forcecloses like original cm7 ?

I will flash if someone convinces me.

I currently run MIUI
[Nexus S Android Development] thegtfusion:
Check my post in the franco kernel thread
[Nexus S Android Development] LibertyMonger:
All I did for now is disabled deep idle and overclocked to 1200mhz and its been zoomin fast again. I learned my lesson, just need to work the settings and figure it out, I am used to my milestone XT720 where we never had to play with any voltage or deep idle settings since the bootloader is locked and never had the privilege of trying different kernels.
[Nexus S Android Development] keith3b:
Anyone with similar issues?

Can anyone help - I feel like I tried everything! Phone draws 80-130Ma idle and 250-400Ma in use, I have tried everything even with background data off. The picture below had background data off for about half the time in the begining. I have also tried a clean install without ANY apps for a day or two - still poor battery!
[Nexus S Android Development] thegtfusion:
Well. So i suggest you wipe dalvik cache when flashing a new kernel?. Im using it with the latest franco kernel. Ill post my graph.

Its charging now. I flashed some roms today so that are the sudden drops. But overall i get a day or one and a half day. Usage: whatsapp, xda and beejive msn. So moderate usage. The kernel settings: deep idle on, rest is stock.
[Nexus S Android Development] keith3b:
I know others are experiencing better battery - like you. I have always wipe delvik and have done complete wipes. My most recent wipe was wiping everything 2x, including formatting system, delvik, wiping all user data (all through CWM), then formatting SD card, then mounting to the computer and pulling NSCollab on through there. It is as clean of an install as you can get. Is there a fatal flaw on some of these phones I dont know about? Did I get a dud?
[Nexus S Android Development] thegtfusion:
Try wiping the battery stats in CWM.
[Nexus S Android Development] keith3b:
Thanks - I know you are on your phone, but in the original thread I mentioned that I have tried wiping my battery stats, then "training" the battery (full charge, to full discharge, to full charge). Then waiting about a week for the stats to populate enough to have a good reading - definately no luck. Here I go - leaving now at 100% - I will be at 30% by 10pm EST with moderate usage.

I am just surprised as I dont see others posting about this poor of a battery. I came from a Captivate and was getting prob 4x the battery life with speedmod kernel and cognition ROM. Also, as mentioned before - franco's Rom didnt have the problem as bad as NSCollab - I guess I may be stuck with a bad phone?!
[Nexus S Android Development] thegtfusion:
hmmm thats odd.

what I do when I flash a new rom:

-full wipe

-wipe cache/dalvik cache

-format data/boot/system

flash rom

flash kernel.

when I'm already on a rom and I want to flash a new kernel I wipe dalvik cache and then flash the kernel.

I once had very poor battery life with NsCollab yes no matter what kernel

I downloaded the stock OTA roms for my model and flashed it, i unrooted locked bootloader etc

so I left the stock rom for about 3 days and with full cycles. (with the stock android kernel)

then I got back in the business and I got massive improvements in battery life.

That worked for me, maybe it will for you. if not maybe use the new battery you bought ;)
[Nexus S Android Development] sabaramo:
I9020t on Vodafone Australia. Running awesome.

Did full wipe using wipe all script then installed ROM and Franco 4 Dec kernel.

Best my phone has ever been. Thanks!!
[Nexus S Android Development] Ok_Kaleidoscope5109:
99% of battery problems are user related and not ROM/kernel related. Usually its a rogue app.

I mean honestly, if you have battery issues you better post your battery use page and let us see the most used thing. If display is taking up 60%, then how can you blame the ROM? Most likely you had your display on a long time. If Facebook is sitting at 40%, then it's the Facebook App. I see this frequently on my phone. How can people so easily attribute things to the ROM?

Look at your reception. When it's bad, battery life plummets a lot more.
[Nexus S Android Development] LibertyMonger:
Yeah everyone's battery would have to be much different, so many variations to make it differ. The best way to tell is to run the ROM a few day's without any apps. Everything is improved then.
[Nexus S Android Development] AnthonyAldrete:
Can someone tell me a good stable release if say I wanted to put a kernel on this rom that has deep idle
[Nexus S Android Development] al_madd:
deep idle??glados for sure,...!
[Nexus S Android Development] Icecoldmeat:
It has, running for 2 days now and 3 FC's, but I dont mind, the ROM is very nice.

Edit: fixed permissions and everything is fine now!!
[Nexus S Android Development] shockem:
Most stable rom I have ever used:)
[Nexus S Android Development] Ok_Kaleidoscope5109:
this rom is dead :(
[Nexus S Android Development] jark99:
Im on .42 everytime i try to flash. 60 or 1 version before it. I get stuck on the google logo..... ive tried this 5 times and yes i wiped everything. Except data, but that wouldnt vause it cause ive updated nscollab before by just wiping caches.
[Nexus S Android Development] mike216:
Format the boot partition in recovery before the flash and you'll be good to go

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] Ok_Kaleidoscope5109:
wipe all/factory reset is always recommended. i've already done that for this ROM, and it's just got issues compared to MV who updates every week or two....

you can't expect a ROM that's received practically no beta testing and no updates to keep up