yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] bkanuka:
Frank went back to the stock kernel with 60 for a byok style rom. You need to flash the rom and then flash the kernel you want.

I would recommend matrix 11. My phones never ran so well as with the nscollab 60 matrix 11 combo. It seems matrix 11 is a great release from the raving that's going on in his forum. And ya it has logcat :)
[Nexus S Android Development] mike216:
I plugged my phone in pc to move some images around. That's about it!
[Nexus S Android Development] uansari1:
Wait at least a few minutes.. My phone was on the Google logo for a bit as well, but after a couple minutes it moved to the boot animation.
[Nexus S Android Development] AnthonyAldrete:
Anyone having issues updating Google music on this new version? Everytime I try I get an error saying incompatible update? Please advise
[Nexus S Android Development] got2best:
Use root uninstaller to remove the current one and then reboot install the new one.. then reboot u may have to reboot a couple times I did.. it will stop force closing.
[Nexus S Android Development] AnthonyAldrete:
Thank you, worked like a charm
[Nexus S Android Development] sakisds:
It worked after all. Now instead of spending time showing the boot animation it stays at the Google logo for a while. Well, since it works, fine with me. Thanks for helping.
[Nexus S Android Development] mike216:
Seems the longer you use it the faster it gets!
[Nexus S Android Development] chinopski:
can i just wipe cache and dalvik cahe if im coming from a previous version of this rom so that i wont lose my data? (im too lazy/scared to backup,wipe data and restore :()
[Nexus S Android Development] bkanuka:
Sorry if this sounds harsh but you should probably read this thread just a little before asking. Its exactly what we've been discussing.

Bottom line is "no" you dont have to full wipe but there seems to be better results if you do.
[Nexus S Android Development] PeXda00:
First time trying this Rom on my i9020a. Had some camera/video trouble at first, even with total wipe. Changed kernel to Matr1x cfs and so far this looking like the fastest and silkiest combo to date. Quadrant score at 3200+ with no overclock. Now that's very impressive.!!
[Nexus S Android Development] ranasrule:
.60 seems a lot more unstable than .50 atleast for me....to many restarts
[Nexus S Android Development] got2best:
Is any1 having problems with alarms not going off?
[Nexus S Android Development] akshayf:
Me too!! At first I thought I ****in slept through the alarm like a monster .... Now I get it...
[Nexus S Android Development] got2best:
Can we fix this frank? Because this is a deal breaker for me... I have to have my alarm.. my phone is my only alarm.. and if u don't get up for work.. :/
[Nexus S Android Development] yashar87:
Excellent ROM

This is the best ROM I have ever seen!

Everything works perfect.

Excellent speed, battery life, excellent performance.

AMAZING multiple languages support everywhere !! SMS, EMAIL , ... (I tested arabic, persian, turkish and english all of them were perfect)

AMAZING multilingual keyboard and even multilingual menus.

Arabic/Persian RTL and shaping support (connected letters everywhere)!

Amazing tools and features.

Huge huge thanks to the developers.
[Nexus S Android Development] RickROM:
No problems here.
[Nexus S Android Development] sano614:
I just tested the alarm and it worked for me...

I just flashed this and wiped data / cache / dalvik. No issues..
[Nexus S Android Development] got2best:
Whenever I test it it works for me also... its only when I set an alarm for hours away... and once in a while it will go off.. but if I set one for a few min away it works.. maybe try setting multiple alarms?
[Nexus S Android Development] jeffkhlam:
i am still using .42, stable for me. have been waiting for a stable update, seems still not time to upgrade yet...
[Nexus S Android Development] Romonster:
you should update, 60 is very stable for me.
[Nexus S Android Development] sano614:
I've set 2 alarms for 4 and 5 1/2 hours from now. Will let you know if they work for me.
[Nexus S Android Development] skitapa:
My phone slowed down to a crawl when I installed my apps. I tried flashing matrix kernel and it's a lot better, however it's still not acting right, it kind of freezes for a second every now and then. Like io or memory problems. The startup is also bothering me abit, the google logo stays way way too long. Does anyone know why the logo remains for so long?

I cleared all cache and all data, however I sideloaded a ton of different quality root apps which may have borked my install.

Sent from my NSCollab 1.0.6, matrix 11 cfs.
[Nexus S Android Development] ssasan:
Compare to my original rom i think this one (60) has reduced display contrast it is now very grayish while Original rom was completely black
[Nexus S Android Development] Ok_Kaleidoscope5109:
with no wipe I tried to set an alarm using Google Voice Search

"Wake me up in 1 minute"

The alarm rang in 1 minute.

Also great work Frank, but after all this time you stuff in Nightly #259??? Are you sure that's stable? So far it is for me. Also might wanna update the OP as it says CM 7.1, but it's actually a nightly right :D

Also, can we bundle in Theme Manager? Iknow not EVERYONE wants it, but it's a CM standard, and I'm sure there's enough people who use it to warrant it at least being included. I think of it this way. A CM ROM should have the bare minimum from CM, and with addons if anything. I don't think things should be excluded unless they're known as terrible features anyway. Theme Manager is certainly not something to be excluded.
[Nexus S Android Development] bkanuka:
If anything is going to be an option id say wallet should be. For me its completely useless and I bet its the same for others...
[Nexus S Android Development] Soldier Blue:
I switched from Matr1x BFS to CFS and it seemed to make a slight impact on the slowness I described earlier, but not much. I'm not very particular on raw performance as long as everything is smooth, and I've compensated by overclocking.

However, I noticed after getting a call from a long sleep/idle that I still can't hear the other person on the line. They can hear me just fine, but I have to hold/unhold the call before we can talk. I had this problem on 0.50 and on Nexus MV rom, but not on 0.39.

I know a lot of people had the mute calls issue in the past, but I'm not sure of the perma fix for it. Can anyone help? It seems to only happen when the phone has been idling for several hours or longer.
[Nexus S Android Development] uansari1:
He includes it as a flashable zip.. What's so hard about that?
[Nexus S Android Development] Ok_Kaleidoscope5109:
because we now have to flash a kernel on top of the theme manager?

At what point is it acceptable to start stripping stuff out? If anything CM based ROMs should have the bare minimum that the CM package does. Most CM based ROMs are designed to be tweaks, so they ADD on to what CM has.

What if you stripped out CM and made it a 10 parts you have to flash separately? Would that be ok? What I'm saying is enough people use Theme Manager that it *should* be an included component. If you don't want it that's fine.
[Nexus S Android Development] uansari1:
What you're not realizing is that it's much easier to install theme manager via flashable zip than it is to remove it if it's built into the rom due to the libs, etc. Believe me..this is the most efficient way for everyone to have choice and only install if you are sure.
[Nexus S Android Development] Ok_Kaleidoscope5109:
you can't remove via titanium backup? and whats the point of removing.

There are other parts of CM that people might not want. I don't think it's the right way to start segmenting parts of CM out and saying to flash everything separately.... The fact remains that Theme Manager is a default CyanogenMod app thats bundled with the CM ROMs. I don't think it should be taken out just because a few people don't want it. Plus there's no harm in leaving it there. The reasons for leaving it out are very limited.
[Nexus S Android Development] uansari1:
Bro, stop complaining how Frank runs his rom and switch to another cm rom then.. Jeebus.
[Nexus S Android Development] mike216:
+1 I can't find anything wrong with it! Lets be grateful guys

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] got2best:
Hey so do u have any update if the alarms worked? I went back to. .50 and c if they work for me tonight..
[Nexus S Android Development] Ok_Kaleidoscope5109:
I'm not complaining. I'm offering a suggestion.

Honestly, every ROM is based on feedback, and good ROM makers take in feedback and reflect on it. You're saying that if there's a problem with any ROM that we should just switch to another ROM? I love NSCollab, but I feel like the inclusion of Theme Manager would make it a little better. I don't think its productive to say that I should switch to another ROM. That's like saying take it or leave it. I mean if you don't care for the inclusion, that's fine, but don't tell me my suggestion is worthless because I should accept the ROM as it is or go to some other ROM.
[Nexus S Android Development] mike216:
You know you can just flash it and if you want it included then get 7zip and go into the flashable zip and copy the theme manager apk into system apps folder in the nscollab zip before you flash it :-)

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] at428hk:
hi if i come from 1.0.50 do i still need to wipe data/factory reset?
[Nexus S Android Development] akshayf:
Naah..... You are good to go.... I did the same without any hiccups. Best of luck
[Nexus S Android Development] Romonster:
No only cache and dalvik wipe will be fine but data wipe is recommended for best performance.
[Nexus S Android Development] sano614:
Both of the alarms worked fine. I also set more alarms while I was cooking and everything worked fine..
[Nexus S Android Development] skitapa:
I went into cwm and cleared cache and dalvik, fixed permissions and then used autostarts to stop all unnecessary apps at boot. Flashed matrix 11 cfs, liveoc 110 stock voltages and disabled nstools set on boot, so I would get the default io scheduler and default settings. I later changed io to none(fifo) and now the phone is blazing fast, no stuttering, and very stable. Thanks frank and mk95 :-)
[Nexus S Android Development] uansari1:
Theme Manager being separate is NOT a problem. Frankly, it saves a lot of us that enjoy stock Android more work by having to remove unnecessary apps.
[Nexus S Android Development] got2best:
Hmmm.. maybe I should do a wipe? Because I noticed last night only my second alarm went off.
[Nexus S Android Development] rub1k:
C:\>adb logcat
Unable to open log device '/dev/log/main': No such file or directory

Strange... this is with morfic's 11/16/11 TEUV kernel after upgrading to 1.0.60 (from 1.0.50).
[Nexus S Android Development] polobunny:
I think morfic might have disabled logcat in his latest kernel(s). If so, you can load them as modules with insmod. Probably in /system/modules.
[Nexus S Android Development] sano614:
Try wiping. Make a backup first so in case it doesn't work still atleast you can restore to where you are now with all your settings and such.
[Nexus S Android Development] nosfaratu:
Well, I installed new version of the new rom, and saw already the first reboot, this afternoon ..

The kernel is the same that came with the rom, I did not change.

When I put the rom, I wipe everything, formatted and everything!

The nexus did reboot, and had half an hour, only to show the "X" the nexus, I will take up the battery and start it again ..

What all this because?
[Nexus S Android Development] frenccw:
From experience it is usually kernel related. The only thing you can try is switching between franco's, matrix and glados (i've only tried these 3 :P) and see which is most stable for you.
[Nexus S Android Development] irizwan:
Re-download and re-flash

you should wipe cache/data/dalvik/boot/system

then install the rom

then restart at the "welcome" screen do not touch the screen let the phone sit there for about 5 mins

then restart the phone again and continue using it =]

hope i helped.
[Nexus S Android Development] nosfaratu:
but I did it all before for the rom!

I'll try other kernels ..

to see if it works or not ..

And also in places where the network was now not so much catch as well ... I have the radio XXJK8..
[Nexus S Android Development] Romonster:
You are using an ancient radio. Try flashing xxKF1 (the newest one).
[Nexus S Android Development] jark99:
Can we have a change log for .60? Thanks!
[Nexus S Android Development] Heeter:
Hey all,

.60 is finally coming around for me. I am still having issues with playing videos and music.

When I am listening to my full version of PowerAmp, about 5 songs into my playlist, it locks up and reboots.

When I listen to my Tunein radio as well, about 10 minutes in, it locks up and then reboots.

Youtube, and media players all do this.

Wasn't doing this with my previous setup (1.0.50)

Any ideas?

Thanks

Heeter
[Nexus S Android Development] saranyan:
Try raising voltages by 25. Across the board.
[Nexus S Android Development] Heeter:
This is what I got with proton.

Heeter
[Nexus S Android Development] syntax_gosong:
This is a good custom rom i ever taste.

No freeze and self restart while in cpu greater than 1GHz (dont use 1,4GHz).

There's CM7 kernel that allow me to make some tweeks & theming.

Unlike any cRom... Flash light doesn't turn off while the screen locked, this is the best part.

Voodoo sound..!!! I like it so very very much... Thanks :D

But the back is heat up often.
[Nexus S Android Development] Ok_Kaleidoscope5109:
honestly, the voltages shown are already stock voltages. raising voltages past stock voltages isn't gonna save your phone. there's probably something wrong.
[Nexus S Android Development] alessandro_xda:
i've been waiting for this update for a long time and after a couple of days testing this are my considerations:

Pros:

a-for the first time i've seen my battery at 100%

b-battery life is increased

cons:

c-battery behavior is quite strange (see attached picture)

d-two days out of two my phone 'died' and

no wake up alarm

!!!

e-boot sequence is really sloooooooow

final consideration:

the most important issue (from my point of view) the 'd' one hasn't been solved so even if the developer made a good job i decided that my experience with nscollab came to an end.

bye

Alessandro
[Nexus S Android Development] akshayf:
Reverted back to 1.50 . It's a pretty unstable ROM. Not blaming frank but the n259 itself is very unstable. Lots of users have reported this...
[Nexus S Android Development] Heeter:
Yes it is,

It's 259 itself, not nscollab

Just tried 259 nightly, and I am having the same issues.

Heeter
[Nexus S Android Development] keith3b:
Battery Life - Help

So although I havent posted, I have been using NSCollab for a while now. I have tried many Kernels/Radio's but get terrible battery life with this ROM. I recently flashed to Bugless Beast and had much better battery like (like 3-4x the battery life) but missed the NSCollab features. Is there something I am doing wrong? I always wipe phone before install, and have "trained" the battery before. For example today I was fully charged at 2:30pm - heavy usage and I was at 35% by 6pm (music and texting for a large part of the time). When I just leave the phone sit off, I am getting drain of close to 10% per hour in idle. I have monitored battery usage and nothing is out of the ordinary (display is the biggest user). Android OS shows up, so does Cell standby and whatever apps I used. Any suggestions? I have tried with Trinity, Matrix, Frano, and Glados Kernals. KB3 radio mainly, but have tried others. Oh, also purchased a new battery just in case it was that. Phone: AT&T 9020A
[Nexus S Android Development] Ok_Kaleidoscope5109:
Ok, there's several things wrong with that. If you wanted Stock android, you would go to AOSP with little mods.

Frank includes a lot of utilities in this rom like:

1) Voodoo Control

2) Explorer

3) ROM Manager

4) Superuser

5) Rescan Media

The list goes ON. I can bet you there are just as many people who don't use those individual apps as they dont use theme manager. Why are you so against Theme Manager but you're not against these apps? The point is Theme Manager is a CM packaged app in the base CM7 ROM. I'm advocating to put it in because this is a CM-based ROM. If you don't want to use it, that's fine. I don't use Rescan Media or Explorer, but I'm not gonna go crazy like you saying NO leave it out, etc etc. Whether or not Theme Manager is there doesn't even hurt you one bit.

Look, I know it's an easy thing to just flash Theme Manager on top of the ROM, but I'm saying that it's better if we didn't have to do this. I already pointed out that if it's so easy to just flash that, what if Frank made a separate flashable every little component of this ROM? Would you be happy then since you want a bare bones ROM?

In the end it's his decision to put in Theme Manager or not as a default. I'm advocating for a yes. I'm not saying what he did was a bad job. This ROM is great. After all this is a thread for discussing the ROM so maybe improvements can be ongoing.
[Nexus S Android Development] mike216:
Handles UV and liveoc extremely well

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] Ok_Kaleidoscope5109:
Is it me or the boot is really slow and sometimes the phone feels sluggish? I did a full wipe from .50
[Nexus S Android Development] mike216:
Boot is really slow but the rom feels fast oddly enough I didn't have good speed until I went through a bunch of different kernels like matrix the glados then back to matrix

On the first run with matrix installed rite away it didn't feel quick but like I said above it now feels extremely good! Stable and perfect with this bad ass ICS theme

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] Breno999:
Mike216, what is the name of your ICS theme?

Thanks in advance!
[Nexus S Android Development] Ok_Kaleidoscope5109:
I feel the phone getting stuck on simple tasks though. Not sure what's going on. Sometimes it takes like 15 seconds to open my email after using the notification pull down menu for example
[Nexus S Android Development] mike216:
Ice cream sandwich theme by Sonny sekhon it looks much better then the screen shot can show

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
You need to try a different kernel my friend! Different strokes for different folks,you could also make your minfree adjustments more aggressive I think that would help you

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
Another important thing is I switched to ADW EX launcher because its way faster then the stock gingerbread launcher that comes with it and very smooth!

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] Ok_Kaleidoscope5109:
Been using matrix 11 which is what I used on 50. Frank didn't change the Minfree settings

So really the only thing that's changed is the rom version
[Nexus S Android Development] SA-07:
change ur sig ;D

it says 8.0 lol
[Nexus S Android Development] mike216:
Try using adw launcher, something is wacky with the stock gingerbread launcher

NSCOLLAB / BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] benrees21:
Or he could try Launcher2

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] Ok_Kaleidoscope5109:
the issue is that it hangs up in programs sometimes. Like it might take 5+ seconds to launch maps sometimes. I don't know. It's NOT the launcher. Or when scrolling page to page on my launcher sometimes it takes like 0.5 secs before the phone reacts. I'm not sure why that is. It may be something with the governor?

I'm just comparing my exact same setup on .50 and .60. I'm running the same apps. Sure I could change everything out, but I'm not sure why 0.60 is running more sluggish. I did a clean wipe and stuff. Both on Matrix 11, etc. The only thing different is the ROM.

Also one thing I kinda question is this ROM. I know Frank has been absent for a long time, but all of a sudden he tells us there's a release and bam it's #259 nightly. Now, either this means Frank did a really crazy job of testing #259 in the time after it was released until the release of Collab 60, or he just threw in the latest nightly without really verifying much. It's kinda bugging me, because he makes great ROMs, but at the same time how can you toss a nightly in without thorough testing? Shrug. Or maybe he has been working night and day while we were quiet and testing nightly after nightly til he arrived at 259, but given how busy he said he is... dunno.

Anyway, I still appreciate the awesomeness of the NSCollab ROMs.
[Nexus S Android Development] nosfaratu:
my nexus with this rom, within 12 hours, so I have 74% battery!

So I sent some messages and I was there for 10 minutes on the Internet via wireless!
[Nexus S Android Development] jman310:
My experience... upgraded from .5 to .6, wiped data and cache (usually dont do data, but have backups anyways that I restore). Works for me without hitches. Alarms work for me. No real noticable speed improvements really. I as well use adwlauncher instead of the stock. I also used matrix 11 bfs and the kf1 radio.

I upgraded the music app as described in the other post. In case anyone missed it, just remove the old music app through titanium for example, restart, and then you can actually go through the market and download it and it'll install fine. Only did the music app because of the fc's I was getting with old version, new one seems OK so far.

Excited for ICS which Im sure frank has and is testing out a bit. Quite a number of ways to go I suppose, depending on what cm does and others. Ive actually jumped the ship for a bit to test out ICS since it's available. No issues on my end that I can see off the top and it runs smoothly. You can download at here if you are so inclined (def do a wipe data and cache for it, I downloaded to sd card, restarted in recovery, and did everything manually). Good luck frank and look forward to what you come up with.
[Nexus S Android Development] nosfaratu:
well, my battery charged to 18 hours, 44 minutes, I only have 44% battery!

I made two calls and messages!

I have the kernel of the franc.

Some help to last longer?
[Nexus S Android Development] Soldier Blue:
I upgraded to 0.50 from 0.39 and got the mute caller issue where the person can hear you but you can't hear them. Upgrading to 0.60 didn't make it go away. I tried Matr1x 10.5 and 11 both BFS and CFS. I tried GlaDOS 1.9 both CFS and BFS. I tried various different CPU governors, disabling deep-idle, increasing cpu min, and suggested fixes like turning off vibrate-on-answer. Nothing makes it go away. The only temp fix I have is to place the caller on hold then unhold.

I also got this problem with Nexus MV rom and every time I change or upgrade I wipe data, cache and dalvik. I format boot and system just in case as well. Researching the issue shows people getting it back in build 20 or thereabouts, while 0.39 was rock stable for me.

It either seems like a long standing and obscure bug in CM7, or something that manifests for various reasons. Does anyone have any information I may have missed out, or should I just cut my losses and go ICS or stock/AOSP?
[Nexus S Android Development] got2best:
What u should do is go into recorvery and then advanced and wipe battery stats.. charge phone then shut it off and let it charge until it showes its full (should vibrate and show full battery) then wipe battery stats again.. after this u will have bad battery but let it die completely then charge it all the back to 100% without interruption.. and do this a couple times everytime your battery life will improve. And soon it wool b great.. :) hope this helps