yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] frank707:
Did you previously apply the fix for FC boot loop due to the toggle widgets? If that is the case a full wipe is required. The SQlite fix disables the toggles.
[Nexus S Android Development] Ok_Kaleidoscope5109:
i did a full wipe, but i've always been restoring apps + system settings from Titanium Backup. Hrmmm... where is that data stored?
[Nexus S Android Development] akshayf:
The sim toolkit app still doesn't work!
[Nexus S Android Development] benrees21:
It won't work on NS period.

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] frank707:
Hate to release another update ;) but google wallet is ready in .51, however google wallet does require a full wipe to function properly. Will wait for some additional feedback on .50 before releasing.
[Nexus S Android Development] rip_noob:
I'm still on 1.0.42 but can you check if voodoo control is the latest version? Or make it optional like dsp manager. Cus I had some problems updating it through the market.

Other than that, rom is perfect for me.
[Nexus S Android Development] mike216:
50 is working great for me been running for around 7 hours

Checked all apks and played some videos,no problems but I'm one of those people who have never had any problems and been running since the first day 39 was released

Maybe some others who were getting issues in the past chime in on how its going for them

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] frank707:
Will update the app and fix this on the next release.

Sent from my Nexus S
[Nexus S Android Development] callummr:
There is one issue I have with NSCollab. It's not even a functionality thing, but the bottom of all dialogs has these out of place curved corners which fit nowhere in the UI. It's just ugly, not mentioned at all in the OP and nobody else seems to have noticed it.

It's just so out of place I get sick of it on every dialog and have to switch to plain CM7 without any of the benefits of this ROM. If anybody knows how to fix this, or even why it's still present, I would be very appreciative.
[Nexus S Android Development] EonHawk:
I wouldn't. At least not yet. Problem is, Google Wallet still doesn't work with most credit cards, or places outside the USA. For that reason alone I would hold off on it.
[Nexus S Android Development] mike216:
+1 if its going to not work properly or be problematic is there any way to keep it out separately to flash as an ad on like dsp manager

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] uansari1:
+1.. Please leave it out for now.
[Nexus S Android Development] sTiCkY88:
meh.. i get reboots while playing muffin knight.. lol.. maybe stock voltage isnt enough for my phone.. gonna add moar..
[Nexus S Android Development] Ser Gilgoroth:
Been using .50 for about 10 hours, seems solid thus far. Only did a cache and dalvik wipe.

As for Wallet in the next release, it wont be much use for myself. Others suggested it being optional, that could be cool if it didn't cause havok.
[Nexus S Android Development] mike216:
+1 no wipe

I always go with a no wipe. I figure if I have problems then ill do a full wipe

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] isinisterx:
I don't know if you already know this or not but for some reason sometimes when I'm unlocking my phone a get a massive lag spike for about 15 seconds and then my phone vibrates rapidly and then the lag goes away.

Anyone else have this problem?
[Nexus S Android Development] eiabea:
my phone died again this night :-(

so the most important function from the phone during the day, the alarm clock, didn't work...

frank could you please look into this issue, i know others have the same problems

thanks!
[Nexus S Android Development] ranasrule:
i find this rom almost unusable with Matrix kernels...with others like Trinity,Apocalypse-Talon and Bugless Pete's kernels it works like a dream
[Nexus S Android Development] eiabea:
hmm, maybe matr1x is the reason for all the zombiephones...
[Nexus S Android Development] falconrulz:
Amazing ROM :D

Fast, Stable, constantly updated

Kudos to the developer :)

Nexus S
[Nexus S Android Development] kuldaoo:
Same here, my phone died just now. 30min ago, i used phone normaly. What should we do? in this state the phone is useless.

i have Nexus 9023 after full wipe
[Nexus S Android Development] zaidaiman:
Full wipe + stock voltage + OnDemand freq with 100-1000MHz + ~an hour of Music = crash and reboot.

Just to report, although I don't really mind about this.
[Nexus S Android Development] Kalimdor:
I have zombiephone too ... but it have nice timing always in night with alarm on ...
[Nexus S Android Development] timpoldo:
I wouldn't.

I think it's premature to include a service that very few people (at moment) can use. Officially the Wallet is issued only for Nexus 4G, in other words is useful (maybe...) only in the USA.

Here in Europe the use of credit cards is still very low comparing to USA ... and even less the use of such advanced technology as a Wallet.

I think the best is to leave the possibility to download it by hand.

In any case I appreciate a lot that you ask us all what we think about include it or not.

Thanks!
[Nexus S Android Development] Rotellian:
Im running .42 from Friday last week. I have experienced one instance of the phone not waking up and excessive battery drain along with it. I beleive related to ebay app, for which 'keep awake' seems to drain the battery.

I dont really want to wipe my phone completely to go to the next version as it takes quite a while to get it all back, even with backups. Can i just upgrade by wiping the dalvik cache as the differences between roms is minimal? Or is that unadvisable?
[Nexus S Android Development] AndroidMilos:
I agree also. All of the various versions of nscollab I have tried with Matrix kernel have had too many problems. I switched to Trinity kernels and no problems with same versions of nscollab roms.
[Nexus S Android Development] eiabea:
i don' know "Apocalypse-Talon" ... where can i download this and Pete's kernel for my i9023 with NSCollab #50??
[Nexus S Android Development] benrees21:
http://xdaforums.com/showthread.php?t=1290798 - Apocalypse Talon

www.peteralfonso.com - bugless petes.

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] gioyann:
exactly the contrary for me: NSCollab+Matr1x rocks, NSCollab+Netharky lags...
[Nexus S Android Development] insomnia48:
Have to agree on that! I've been using this rom since version .39 always with the latest Matr1x CFS kernel and it just rocks!!! I updated to all versions released and they were all fine. It's superfast and I haven't had a single issue whatsoever.
[Nexus S Android Development] AndrewWalker613:
Im one of the lucky ones that never has issues I guess too

the only thing I do is underclock to 800MHz since I dont really use my phone too much for gaming.

Im still using .45 tho.

I probably wont flash again till .51 is out so its worth while.
[Nexus S Android Development] mike216:
Yes,I always just wipe both caches when I flash I figure if I run into problems then ill do a full wipe before flashing and I've been running fine haven't experienced any of the issues in the op

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] irizwan:
Full Wiped and installed and is running great havn't experienced any issues as of yet =)
[Nexus S Android Development] akshayf:
Phone in my pocket... Received 3 texts. The phone froze with lights on. Had to pull battery. How's this a stable release i don't know.
[Nexus S Android Development] SA-07:
Settle the f down.

Does that mean you enabled bln in the app?
[Nexus S Android Development] Ok_Kaleidoscope5109:
honestly this version is a little buggy. 39 was the last solid release I used that didn't reboot like mad.

I still have to do more testing on my end, but there's more instances of screen not turning back on, etc. a lot of FCs... and this is with a clean install.
[Nexus S Android Development] mike216:
Bull sh*- I don't know why it works so well for the rest of us

What's really going on?

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] benrees21:
No issues here.

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] akshayf:
Yes I have the pro version of the BLN app and it's enabled
[Nexus S Android Development] SA-07:
Lol I got a little pissed there
[Nexus S Android Development] sTiCkY88:
there seems to be a problem with bln.. or touch wake or something..

when ever I off my screen and touch the capacitive butttons, it turns on..

weird.. doesn't seem to be happening atm..
[Nexus S Android Development] jodtalingchan:
no problem whatsoever
[Nexus S Android Development] jman310:
I've been on the releases since 1.0.35ish, .39 and. 42 were most stable, on. 50 and seems most stable to date. I think most problems are from either apps that are on that are causing issues, tweaks, or poss hardware differences (haven't done much looking into diff between i9020 and i9023). I have 9020 and no problems. Only thing I've seen in past was setting CPU down to under 400 MHz on screen off with set CPU and it not waking, tho assume some timeout in os that maybe timing out? Anyways, haven't tested lately.

As for wallet, I know up in Canada here most credit cards and shops support nfc, tho prob wouldn't throw in wallet quite yet.

Thanks again Frank for all hard work.
[Nexus S Android Development] Ser Gilgoroth:
The different phone variants had me thinking as well. I haven't put much research in it though.
[Nexus S Android Development] Lou2serious:
I just flash this rom after a full wipe. My phone seemed to run real hot without me setting any of the CPU tweaks. I flashed Pete Alfonso kernel and that cured my hot phone issue. Now I noticed when I recorded a couple videos they were muffled and choppy for a split second through out the recording. This rom is fast but still needs some finishing touches. I have a i9020 NS by the way.
[Nexus S Android Development] kuldaoo:
today, my phone was "dead" again. i had to pull battery. it's very annoing :((
[Nexus S Android Development] eiabea:
i flashed Apocalypse-Talon v2.1 to see if the problem is kernel related, and yes it is ^^ today my phone woke me up, no issues so far with this kernel ;)
[Nexus S Android Development] kuldaoo:
Sometimes my phone died after two days, so don't celebrite too early :) i'm testing different kernel at the moment so if the problem happen again, i will try Apocalypse.
[Nexus S Android Development] isinisterx:
Yeah sorry I can't use this kernal anymore either. My phone just froze and gave me yellow lines across my screen. Going back to netarchy
[Nexus S Android Development] SA-07:
Yeah, **** happens.

Lol
[Nexus S Android Development] hkoutso:
Been running .50 since yesterday and everything seems to work fine! Actually its the first time the Matr1x kernel runs fine with no reboots (as of now), oced to 1.2ghz on Lazy governor.

Battery life is good for 21-22 hours on medium usage.

Is anybody here using Setcpu profiles for screen off with the Matr1x and Lazy governor ?

Thinking about trying ondemand governor and setcpu screen off profile to see how much more battery we can get out of it.
[Nexus S Android Development] gratti:
After this update me google music account is not getting synced for some reason. Anyone with the same issue?
[Nexus S Android Development] AndrewWalker613:
I kinda want a link to download .51 lol

I dont wanna install .50 and then have to redo the next day for .51 lol
[Nexus S Android Development] liorry:
Phone dies here too (black screen, turn on/off button won't work and if I connect to USB, screen turns off but no touch input is possible)... with 1.0.46.

Flashed 1.0.50 today, will report back if it'll die again.
[Nexus S Android Development] kuldaoo:
1.0.50 dies too...:-(
[Nexus S Android Development] kemsiro:
OMG !!! this is for the first time NSCollab thread is full of dead phone report @@"

this used to be a very stable ROM
[Nexus S Android Development] saranyan:
Think this had something to do with Latest Cyanogenmod 7.1 stable.

Am running that and after 23 hours the phone died, Nothing working and screen and softkeys were off..
[Nexus S Android Development] Ser Gilgoroth:
Unfortunately I had the dead phone occur early this morning. Black screen, none of the buttons did anything, had to pull the battery.
[Nexus S Android Development] dougcunha:
Same here...with the talon 2.1...
[Nexus S Android Development] 3rdcoast:
So far it seems that BLN made it easier to go into sleep death. I have it turned off now so we'll see if that was it. FYI, when this happens I still have adb access which allows me to do a graceful reboot instead of pulling the battery. But so far it hasn't happened in almost 24 hours with BLN off. If it does I'll try a different kernel.

Battery life however is very good for me relatively speaking so I'm happy with that.
[Nexus S Android Development] benrees21:
I always have BLN disabled and had this sleep of death this morning. I'm on NSCollab.42

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] 3rdcoast:
I don't know what it is either but for me this only started with the updates this past week. .42 etc never did it to me.

As for google wallet I'd vote to make it a separate install since it has little use for most and no use for us outside the u.s.
[Nexus S Android Development] mike216:
Ondemand or lazy will throttle the CPU just fine without profiles. Unless your using a different governor besides those two I feel that profiles are not needed,just my opinion but what the hell try it and see how it goes

Sent from my Nexus S
[Nexus S Android Development] Ok_Kaleidoscope5109:
mathkidd, you have BLN support in your kernel, but you also have baked in BLN right? I believe Frank disabled that, so any BLN we use is a product of your BLN enabled kernel (which practically every kernel has), and the BLN app...

I noticed the BLN errors came in with CM7's baked in BLN support before, but that should be all gone now right?
[Nexus S Android Development] SA-07:
I disabled it for frank but you can enable it in the app
[Nexus S Android Development] irizwan:
Weird i'm runnin .50 and havn't experienced the phone dying lol
[Nexus S Android Development] heyoh:
I've had my phone die on me twice now. Something is definately wrong. I'm just going to hold tight and deal with it and see what shakes out. That being said it is a nasty little issue.
[Nexus S Android Development] SA-07:
Prolly a cm issue
[Nexus S Android Development] frank707:
For this with issues are you restoring backups after installing the rom?

Sent from my Nexus S
[Nexus S Android Development] Ser Gilgoroth:
No restored back up as of yet. Initial upgrade from .46 to .50 just wiped dalvik and cache.
[Nexus S Android Development] arshad14:
Contacts FC with Facebook linked contacts...

Has anyone else noticed the following error for contacts that have been linked with facebook contacts? I'm on NSCollab 1.0.50 with 8.0+ and every time I try to go into a contact from my contact list that has Facebook link, it gives me the message, "Sorry! The process android.process.acore has stopped unexpectedly. Please try again." And I only have the option to FC.

After getting that error a few times, I did a full wipe and redid the entire ROM and did not even restore from TB.
[Nexus S Android Development] Ser Gilgoroth:
Another thought as well, it seems everyone says this is happening in the early morning before any alarms go off. Any idea why it happens when the phone is sorta idle?

I can't confirm this as I don't link any contacts to Facebook.
[Nexus S Android Development] glasslung:
I'm getting force closes from Music. Moments after rebooting my phone I get a message saying process com.google.android.music has stopped unexpectedly.
[Nexus S Android Development] dudekiller:
added contacts aren't working on any of the cm7.1 roms what's going on?
[Nexus S Android Development] zaidaiman:
I have tried power off and pulling out the battery for 2-5 minutes and uninstall titanium backup.

So far didn't get any crash or reboot for a day now with music played > 1hour at least.
[Nexus S Android Development] mike216:
Hmm music apk causing problems,don't use it I like power amp and bln enabled people report problems

I've been running 50 with no problems but I don't use bln have it but barely use it. I tried Trinity even though matrix was flawless for me so I wonder if music and bln are causing all these issues possible in conjunction with touch wake

Before abandoning this awesome rom try the prior music apk and if your getting a lot of reboots try a different kernel until MK sorts it out for the few who are having bad luck on it

I've tried all kernels and matrix has always been stable for me I didn't use 6.0 and 7.0 versions just 5.5 and 8.0 were great Trinity and pete are great too so before going somewhere else give that a shot

I hope my luck holds up though lol.. my model is I9020T maybe people who have issues could post there model?

Sent from my Nexus S
[Nexus S Android Development] Ser Gilgoroth:
i9020a here, I don't use music but I do use the free BLN. Not abandoning this rom. First real bug I've encountered.

Is it worth testing another kernel or is that just going to be a pain?
[Nexus S Android Development] eiabea:
i am on Talon v 2.1 since 2 days and that seams to fix the dead phone issue :)

BLN always on
[Nexus S Android Development] zaidaiman:
I'm on i9020T, with BLN enabled and PowerAmp for music.

So far nothing related with music or BLN causing the reboot issues.
[Nexus S Android Development] skitapa:
I am on 9023 and I installed. 50 the day it came out. I wiped everything and installed, then I used Rom manager fix permissions, and set the Cpu to 1200 lazy gov. I also uninstalled musik, and have not used BLN. I have not had any reboots, nor sleep of deaths, which I have noticed earlier always seems to happen when the phone is idle to long, ie in the mornings, I also noticed that it would seem to wake up if I woke it while charging and could get stuck in a SOD if I first pulled the charger and then tried to wake it. I have not tested it thoroughly though but have reflected over it.

Btw awesome Rom and kernel, Big thanks to Frank and Mathkid for the tremendous job you put in :-)
[Nexus S Android Development] hachoo:
anyone running that ezeekeel deep idle kernel?
[Nexus S Android Development] zirra:
I read on the CM 7.1 changelog that a new feature is touch-to-focus. Since I haven't flashed the new rom yet is the touch-to-focus feature available on the camera app is in this build?
[Nexus S Android Development] mike216:
I don't think so I just tried and went through the camera settings with no luck

Sent from my NSCOLLAB
[Nexus S Android Development] mikechw:
Running for32 hours without reboot after I changed to lazy governor 1.2 ghz.(1.0.50)

B4 I get reboot even on 1 ghz on demand. Something is wrong with the on demand governor
[Nexus S Android Development] Ser Gilgoroth:
I disabled BLN last night, not dead phone, but this also only happened once to me. I am using the OnDemand govenor.

Seems most folks are using Lazy, how's it for battery?
[Nexus S Android Development] mellocello83:
.50 download link error?
[Nexus S Android Development] frank707:
Made some changes to the server. Site and rom manager downloads will be back up in about an hour. Don't have access to a desktop at the moment to set up mirrors. Sorry guys.
[Nexus S Android Development] foethalove:
The past couple of weeks I have had problems with my Gmail sending messages. Composed messages seem to always get stuck in the outbox and never get sent out..wifi or 3g. I have read and performed the fixes where you 'clear data' under applications>manage>gmail and this does fix the problem except it deletes those pending outgoing messages and you have to retype them. It also only fixes the problem temporarily....this is a major problem. Anyone else experiencing this?

NSCollab .50

Edit: Also any changes( deletion, stars, etc ) are not syncing to my web gmail...

- Going to try uninstalling and re-installing Gmail but ill keep this post up in case anyone has extra insight
[Nexus S Android Development] Ok_Kaleidoscope5109:
ok more testing seems to be ok.

Frank, can we get Theme Manager back? It's bundled with CM in general right, so it'd be nice to have it? My touchpad CM7 alpha came with it too! :D
[Nexus S Android Development] Tzorg:
I'm running the Trinity TEUV released today with a fixed version of deep idle on .50 and so far so good. Will know better tomorrow.
[Nexus S Android Development] nosfaratu:
This rom is already stable?
[Nexus S Android Development] skitapa:
Stable is a very loosely defined term. I would say it's been stable enough for daily use for for long. But that's just my opinion ;-)
[Nexus S Android Development] arshad14:
Phone book contacts error

So am I the only one with the issue where I can't see the full details of contacts that are linked to the likes of facebook, linkedin, whatsapp, twitter, skype, and what not?

Every time I go in, it gives me a FC saying that the android acore is not working as expected. I have tried a full wipe and reflash without restoring anything from TB but still I experience the issue.

I'm running on the NSCollab 1.0.50 with Matr1x CFS 8.5. I also have the Nexus Prime boot animation with the Google Wallet, CM Theme Chooser, and DSP Manager installed. I have tried fixing permissions and wiped dalvik cache numerous times but I'm still having issues. Please help :(
[Nexus S Android Development] mike216:
Zedomax wanted to review some good roms so I suggested the best of course! Finally a review on YouTube

Sent from my NSCOLLAB
[Nexus S Android Development] alessandro_xda:
maybe i'm just lucky, but here is what i did...

i had my phone locking with screen off many times a day and decided to investigate about the root causes so i began lo look at my logcat for some minutes and i saw many tries of 'clock updates through the carrier clock'.

this happened many times in few minutes to i decided to disable the auto-update and from that moment on i had no more phone locks... (not a single one in about 4 days).

i know that 2 days are not enought to say that my phone doesnt lock any longer...

i know that i can be a coincidence...

but i wanted to share this experience so other people having the same issue can give a try...

bye
[Nexus S Android Development] saranyan:
Its a cm issue. It'll force close if you have synced the contacts with Facebook. Google contacts work fine for me.
[Nexus S Android Development] jimpaz:
Try uninstall Google+ 3.0 ICS...
[Nexus S Android Development] arshad14:
You are a genius!!! As soon as I uninstalled Google+ 2.0 ICS it fixed all issues with contacts! :-D

Thanks so much!
[Nexus S Android Development] mellocello83:
Well I have to say .50 has pretty much been useless for me. I'm coming from the flawless .39 and performed the usually dalvik and cache wipes, Reboots. Followed the OP and did a full wipe and format boot and getting reboots left and right. I get the phone booted and as soon as I unlock and scroll for a couple of seconds, it freezes and reboots. I made no changes to kernel or performance settings. I also tried re-downloading the .50 zip and it's still rebooting. (I9020T w/KF1)

Sticking with .39 for now. NScollab is still tops for me. Thanks
[Nexus S Android Development] -Nacho:
You could click on his thanks button then...
[Nexus S Android Development] Clusterfunk:
I'm definitely getting more sleep death and random revolts on 1.0.50
[Nexus S Android Development] mike216:
Try raising the voltages 25 across the board except 100 leave that at 950

If that doesn't work raise it another 25 and if you still get reboots then try flashing another kernel

Sent from my NSCOLLAB
[Nexus S Android Development] arshad14:
I would but its not supported on the android xda app :-(