yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] jodtalingchan:
if you could share apk for market 3.1.6, I would greatly appreciate. Now I just stick with 2.3.6 coz it's faster than newer versions

edited: never mind I got it :)
[Nexus S Android Development] DumbUglyDragon:
So you are flashing NSCollab, then flashing another kernel over it? What kernel are you using?
[Nexus S Android Development] mike216:
Your going to need root explorer

Download marvis 10.05 rom that has the new market in it unless you can just go find it,I couldn't

Extract the apk under system/apps

Its called vending not market when you extract it the option will come up and say yes go to extracted

Copy and paste it in the spot where you got it system/app

You can do this with any apk you ever want out of whatever rom you want but you only want to use system apk from gingerbread and data apk are universal (market apks)

Need any further help just let me know

Oh I forgot after you copy and paste the vending apk you will need to fix permissions so hold down on vending apk after you copy the new one over and choose permissions then check write I think its the most top left one that you can check then reboot,it wont take effect until you reboot
[Nexus S Android Development] mike216:
My guess is kernel related atleast it was on the old froyo days
[Nexus S Android Development] sTiCkY88:
i cant kill the process..
[Nexus S Android Development] Cybergr:
Maybe i ll try reflash with stock Matrix kernel and see if something change!!:rolleyes:
[Nexus S Android Development] mike216:
Try that,when you flash the rom before leaving recovery flash matrix 8.0 you can get the same kernel over at the matrix thread the only difference is that kernel is undervolted but with set cpu you can set the voltages that Frank put in that I highly suggest

Frank has been doing lots of testing with his suggested voltages and there reboot free so use them

If you get that far then let me know and ill give you the stock 45 suggested voltages
[Nexus S Android Development] mike216:
Franks new script wipes the dalvik cache for you but I manually wiped mine and everything worked perfect along with wiping data so that's what I highly suggest

If your one that hates setting everything back up then just backup all your data apps with titanium backup and restore data only after doing the market sync and everything restores

I have 0 issues doing it this way
[Nexus S Android Development] Rotellian:
Something weird just happened. Installed the ROM yesterday, been fine, but just went to look at my phone and the power button wouldnt wake it up. Pulled the battery and when it booted back up my phone was down to 20% battery (from 50% when i left it).

Ive checked around a bit and the battery usage reports the ebay app as having been in Keep Awake for just over 3hrs.
[Nexus S Android Development] 3rdcoast:
I've had the "sleep death" twice now. I verified the 2nd time that the phone was still alive and could do adb reboot. Otherwise there's no reaction on the phone when this happens. All seems fine at reboot. I did have the stand alone v8 kernel on it before flashing 1.0.45 but assume that the flash overwrote the kernel with stock settings?
[Nexus S Android Development] tankmaster90:
I've had that happen to me too. I think what happens is the phone somehow freezes and is I guess constantly on in a way that drains battery. So until you notice it to pull the battery your battery is being drained fast. And when you look at the battery usage you see this jump.
[Nexus S Android Development] Cybergr:
1st of all thank u for ur replies and suggetions!

I had re-flashed the NSCollab 1.0.45 Rom and i will test it with the stock Kernel to see whats going on...cause yesterday i preferred in my first boot to use latest Trinity T144, seems more stable for me when i want to play with O/C and benchmarkings haven`t got any restart yet when i run 1.440 Mhz and seems pretty stable even when i run at 1.540 Mhz - *Antutu although get f/c at 1540* - .With Matrix 8 and v42 i couldn`t go more than 1300Mhz...!!

I ll try and post back..!!

If u can so i would like to know the exacts voltages values that Frank use in the latest 45 release..Can i get them from inside of SetCPU app..?!

For now i am on stock 45 kernel..!!

Thanks again!!
[Nexus S Android Development] SA-07:
Hello there my kind sir, why doncha flash v8.0 from my thread and oc ur heart out ;)
[Nexus S Android Development] SA-07:
For y'all having bad experiences, just flash v8.0 from my thread and ur problems will be solved
[Nexus S Android Development] Cybergr:
I will try it tomorrow cause with NSCollab 42 and ur Kernel 8 as i said before haven`t made it more than 1300 Mhz..!!
[Nexus S Android Development] SA-07:
I mean you are running it like 144% above the normal clock speeds and some phones just can't handle that haha
[Nexus S Android Development] Cybergr:
Yes i know that i am running it really high..but why with Trinity kernel my device can handle that cpu frequencies and with v8 not?
[Nexus S Android Development] SA-07:
Cuz ur phone likes those voltages more than mine haha
[Nexus S Android Development] Cybergr:
So if i wanna stick with ur kernel i have to simple use Trinity`s kernel voltages..?!Thats what i was thinking doing cause i really like ur effort here!!

Is there a workaround to find and edit voltages on kernel`s?!
[Nexus S Android Development] mike216:
Yes that's exactly where you can find the voltages
[Nexus S Android Development] mike216:
This comes with 8.0+ did you tweak your 8.0 version some more

I feel really lucky that so far I haven't had the reboot problem I mean I got 1 reboot but I've been running this rom ever sense the first day 39 droped but if I start to get them all I have to do is start gradually raising the voltages? I thought the problem was from all the different things that are build into the rom or ram management issues.Is that the solution MK

What's different from your 8 and franks 8 besides the voltages
[Nexus S Android Development] SA-07:
Bln is disabled in v8.0+ that's it ;)

Everything is the same tho
[Nexus S Android Development] isinisterx:
Few questions :

1. Are the voltages stock when I fresh install the rom?

Asking this because I would rather not overclock / overvolt my phone.

2. The stock calendar is force closing for me. Any way to fix this?
[Nexus S Android Development] mike216:
Frank bumped up the voltages a little for stability and it safe boots at 1000mghz so your good to go and go in recovery or rom manager and fix permissions to solve your calendar force closing on you
[Nexus S Android Development] mike216:
If you don't want to overvolt whitch you should trust franks judgement but if your dead set on having stock voltages then here you go,you'll need set cpu

1400-1440

1300-1400

1200-1350

1000-1250

800-1200

400-1050

200-950

100-950

Thanks to MK for providing me with these
[Nexus S Android Development] SA-07:
No problem mike.

I just want to note that the voltages are different in 43 and 45 tho

This new one has much different voltages than the 43
[Nexus S Android Development] SA-07:
Tbh, I can't remember if it was the 43 or 44

Flash both and take a look in setcpu --> anyone who has the time to, id really appreciate it!! It will help all of us who are unsure about the voltages
[Nexus S Android Development] SA-07:
So basically, if someone can start at .43 and keep going, noting down the voltages
[Nexus S Android Development] SA-07:
Alright guys frank and I have been discussing about this and we are deeply sorry for any problems you guys have had.

We are going back to stock voltages, as they will be much easier to follow and tweak. Thanks Mike for posting those!!
[Nexus S Android Development] mike216:
Something is definitely wrong with the script Frank 45 installed fine on my phone but will not boot on my coworkers phone wiped everything and no luck
[Nexus S Android Development] DumbUglyDragon:
I think some devices are just more picky than others when you mess with the clock speeds. Mine on any ROM: 1400MHz = instant crash, 1300MHz = crash within 10 minutes, 1200MHz = crash within a day or two. :( It just doesn't like to be messed with lol
[Nexus S Android Development] SA-07:
Don't worry, we are coming out with a better release
[Nexus S Android Development] DumbUglyDragon:
No problem. .42 works fine for the time being... I just need to figure out this market glitch :confused:
[Nexus S Android Development] frank707:
.46 Fixes the boot issue with kernel adjustments. Sorry guys, ran fine on our test devices but seems that it didn't play well with the rest of you.

If you continue to run into boot issues please format /boot through "recovery - mounts and storage, before flashing the rom.
[Nexus S Android Development] DumbUglyDragon:
Thanks, .46 booted up just fine.
[Nexus S Android Development] jishnu7:
While on call, headphone button action is mute instead of default end call. Is this a bug or feature?

If it is a feature, how can I get back the default end call function?

Am now on .46
[Nexus S Android Development] -Nacho:
Installed .46 a couple of hours ago - everything working fine so far. Thank you for your work!
[Nexus S Android Development] :
News :) about netarchy

Changelog:

Revision 1.2.9:

- Voodoo Sound v5 driver update

- Adjust default colours to avoid the initial "Yellow tint shock"
[Nexus S Android Development] kassemalaa:
touch sensitivity

hey, i've been on Axura for quite a while now and decided to check out NSCollab just for a change. Im loving this rom so far, but my only concern is with the touch sensitivity, it seems less responsive on this rom, especially when scrolling a list, sometimes ill swipe my finger on the screen and it would not even react... is anyone else experiencing the same issues as i am? and is there a way to increase the touchscreen senstitvity? thanks!
[Nexus S Android Development] kevin_ngckk:
same here when i scrolling the home screen.
[Nexus S Android Development] Jibreil:
I too find the touch sensitivity weak on v1.0.10

The issue could be relating to the build Nightly #22
[Nexus S Android Development] kevin_ngckk:
I think so. And another problem is the battery life also weak than the previous version but its smoother... i dont have oc at all. BTW, this rom is great;)
[Nexus S Android Development] JmPTaz09:
No touchscreen issues here, 1.0.10 running smooth as butter, all functions working great!
[Nexus S Android Development] dont know:
No, the 2G/3G switch via energy-status-bar crashes the phone. After a reboot I had a loop-FC of com.android.phone. Try it - if u want to flash again ;)
[Nexus S Android Development] JmPTaz09:
All functions I use* are working well. I don't use 2G/3G toggle; I always want 3G. Everything running great for me, and battery doing well. At 79% after 5 hours with 30 mins screen on, 30 mins listening to music and a bit of facebook browsing; not bad. CPU governor set to conservative. GPS is also working again; on 19 it wouldn't work once I toggled it off for some reason, and I tried that on regular 19 and the last NSCollab based on 19.

And no, I don't want to flash again! :)
[Nexus S Android Development] serrov91:
Reading the reviews users write about NSCollab, I had to give it a try.. I had enough of random reboot, loss of signal and all with the CM nightlies.. Flashed NSC 1.0.10 tonight from a clean wipe (USB wipe, data factory wipe, dalvik, cache, and fixed permissions).. gonna report how good is this promising alternative ROM going for me!:rolleyes:
[Nexus S Android Development] JmPTaz09:
Flashed Netarchy 1.2.9 cfs on top of NSCollab 1.0.10, all appears to work well and brings the full functionality of the latest Voodoo update.
[Nexus S Android Development] lfmmoura:
Working great here with Netarchy 1.3.0. Only issues so far are the 2G/3G notification toggle (DON'T use it) and update auto-notification for cyanogen (doesn't seem to be working yet.)

All in all, it seems very stable.
[Nexus S Android Development] RickROM:
I did the same thing also . . . no problems so far, and it's wicked fast!
[Nexus S Android Development] zephiK:
Might want to update that to 1.3.0 ;) Even faster.
[Nexus S Android Development] frank707:
Will release an updated build with 1.3.0 for thoose with delayed boot times.

For update notifications for NSCollab they are available in Rom Manager (Premium).

Sent from my Nexus S
[Nexus S Android Development] frank707:
[03/19] 1.0.11

[system] CM 7 Nightly #25 [improves touch screen sensitivity and scrolling :) ]

[kernel] Netarchy 1.3.0 CFS [improves boot times]

[update] Busybox 1.7.1

[update] Voodoo Control [v. 0.10]

[mod] CMParts.apk [removed System CM specific options ex. System /CMStats /CMUpdate /Changelog]
[Nexus S Android Development] kevin_ngckk:
thanks again!!:p:p:p:p:p
[Nexus S Android Development] kevin_ngckk:
Everything is fixed. no more the screen sensitivity problem.This rom had been prefect"ed' after i flashed 1.0.11. If there is any issue i will report!
[Nexus S Android Development] imneo1:
Delay in Boot ?

After upgrading to NSCollab-1.0.11 with netarchy-1.3.0.0-cfs

I

still

notice the delayed boot, probably because of this: (SurfaceFlinger)

I/SurfaceFlinger( 505): Client API: OpenGL ES
I/SurfaceFlinger( 505): EGLSurface: 8-8-8-8, config=0x1
I/SurfaceFlinger( 505): OpenGL informations:
I/SurfaceFlinger( 505): vendor : Imagination Technologies
I/SurfaceFlinger( 505): renderer : PowerVR SGX 540
I/SurfaceFlinger( 505): version : OpenGL ES-CM 1.1
I/SurfaceFlinger( 505): extensions: GL_OES_byte_coordinates GL_OES_fixed_point
GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_p
aletted_texture GL_OES_point_sprite GL_OES_point_size_array GL_OES_matrix_palett
e GL_OES_draw_texture GL_OES_query_matrix GL_OES_texture_env_crossbar GL_OES_tex
ture_mirrored_repeat GL_OES_texture_cube_map GL_OES_blend_subtract GL_OES_blend_
func_separate GL_OES_blend_equation_separate GL_OES_stencil_wrap GL_OES_extended
_matrix_palette GL_OES_framebuffer_object GL_OES_rgb8_rgba8 GL_OES_depth24 GL_OE
S_stencil8 GL_OES_compressed_ETC1_RGB8_texture GL_OES_mapbuffer GL_OES_EGL_image
GL_EXT_multi_draw_arrays GL_OES_required_internalformat GL_IMG_read_format GL_I
MG_texture_compression_pvrtc GL_IMG_texture_format_BGRA8888 GL_EXT_texture_forma
t_BGRA8888 GL_IMG_texture_stream GL_OES_egl_sync GL_IMG_vertex_array_object
I/SurfaceFlinger( 505): GL_MAX_TEXTURE_SIZE = 2048
I/SurfaceFlinger( 505): GL_MAX_VIEWPORT_DIMS = 2048
I/SurfaceFlinger( 505): flags = 00010000
D/SensorService( 505): nuSensorService starting...
D/libEGL ( 515): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 515): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 515): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 515): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
[COLOR="Red"]E/SurfaceFlinger( 505): eglSwapBuffers: EGL error 0x3008 (EGL_BAD_DISPLAY)[/COLOR]

can anyone confirm ?
[Nexus S Android Development] RonnieRuff:
Mine is much faster.

Sent from my Nexus S
[Nexus S Android Development] serrov91:
I flashed the 1.0.10 yesterday evening and had three losses of signal resulting in some kind of "SIM card reboots" asking me to enter my PIN code...

Flashed the 1.0.11 this afternoon, running great for the moment!
[Nexus S Android Development] isinisterx:
Thanks

I'm underclocking it to 800 mhz for battery life and it seems stable
[Nexus S Android Development] akshayf:
This muted caller issue is seriously getting out of hand now. Aaaaaarrrrrrrggggghhh
[Nexus S Android Development] Fidel Cashflow:
Wondering if anyone else has this issue. After running quadrant (mainly for curiosity purposes) the launcher screen seems to take a while to populate. I'm runnning it with ondemand at 1200 mhz.

Also I can't tell if I messed something up or if it never did this in the first place but I can't seem to get the home screen to change orientation.
[Nexus S Android Development] frank707:
Try removing the DSP manager. I can't seem to reproduce the issue. Let me know if that gives you any results

Sent from my Nexus S
[Nexus S Android Development] mike216:
Its gingerbread brother so no Orientation
[Nexus S Android Development] mike216:
Frank 45 has been running great for me could you please tell us the difference in kernel tweaks between 45 and 46

I use power amp so not sure I need to go to 46
[Nexus S Android Development] Fidel Cashflow:
Thanks, my Nook Color does orientation that's why I asked (I assume you mean stock gingerbread not gingerbread in general).
[Nexus S Android Development] mike216:
Yep gingerbread launcher

cool name
[Nexus S Android Development] mike216:
Got lazy and updated without a wipe since 45 and 46 are so close,is it possible I can loose speed by not wiping or is the wipe suggested to prevent bootloops and force closes any help would be greatly appreciated and have a thanks on deck waiting for any cleverly helpful nscollab friend
[Nexus S Android Development] bunilla:
Come on solve this allready... does anyone have any idea what's causing this?
[Nexus S Android Development] mike216:
This is what I was referring to Math kid
[Nexus S Android Development] SA-07:
I am literally confused. What are you asking me? Do you need the changes from 8.0 to 8.0+ in .46??
[Nexus S Android Development] frank707:
Kernel : Matr1x CFS 8.xx + [MATHKID95]

Matr1x + : Stock Voltages

Matr1x + : BLN [Deactivated]

Matr1x + : 100mhz / 1ghz [Default Clock Speeds]
[Nexus S Android Development] tankmaster90:
I'm getting it too :/ Its annoying

is this part of CM ROM or the kernel??

Its still not preventing from switching out of this ROM btw. Its still to good of a ROM to do that.
[Nexus S Android Development] Clusterfunk:
1.0.46 seems to be working for me so far. No horrible reboot loop like with .45.

Good work, man.
[Nexus S Android Development] SA-07:
Glad it works!! Told ya .46 would be better ;)
[Nexus S Android Development] mike216:
Bln is deactivated,that's what I asked about MK.I just wasn't exactly sure what that meant.
[Nexus S Android Development] krazydonutboy:
Quick question, I'd rather be safe (and a bother) than sorry.

Installing updated Collab zip through clockworkmod: will it just upgrade the os, or will all applications, settings, etc get lost also?
[Nexus S Android Development] SA-07:
If you had nscollab you can just flash it without wiping and it will be fine.

I would wipe dalvik cache tho
[Nexus S Android Development] Fidel Cashflow:
I ended up flashing the Matr1x kernel anyways but why was BLN left off in .46?
[Nexus S Android Development] SA-07:
It was just deactivated. You can get the bln control app and enable it
[Nexus S Android Development] irizwan:
Its really weird that people are having probs with NScollabs builds i've been running Nscollabs since .39 i've updated to every build after it :D .40,.44,.45 :P never got boot loops or FC's .. did a clean(wipe dalvik,data,boot) install every time maybe thats why :/

anyways .46 working perfect as always =] +1 Frank and Mathkid
[Nexus S Android Development] Fidel Cashflow:
I forgot to wipe dalvik or cache when upgrading this morning and haven't had any issues at all (from .45 to .46). Seems odd that others are having issues.
[Nexus S Android Development] mike216:
+1

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] -Nacho:
I did get a fc every now and then with .42 and battery drained quite fast. For now .46 running five and great battery life again. Thanks!
[Nexus S Android Development] eiabea:
Very nice ROM, but since .42 i had a strange problem:

Since the update my phone died about 5 times. That means the screen stays black und don't react on any button so i had to pull the battery...in this state the alarmclock don't work so i get late to my job xD

I don't changed the clock or the voltages, just changed the governor from ondemand to smartass v2 with setCPU

anyone else had this issue??
[Nexus S Android Development] frank707:
Download: NSCollab-1.0.50.zip

MD5 : [ 9d0131dc059b04e262f66665591a7187 ]
[Nexus S Android Development] alessandro_xda:
same here (i've been late too!!) without changing anything (neither clock/voltages nor governor).

it happens a couple of times a day and often during the night, so no alarm in the morning :(.

this happened on every single version i've tried (starting from 42)

bye
[Nexus S Android Development] daffyno:
from #46 wipe required master?!
[Nexus S Android Development] eiabea:
just wiped dalvik, cache and battery stats and works great so far ;)

hope that this update fixed the "dead phone didn't wake me up in the morning"-issue :D
[Nexus S Android Development] liorry:
What happened to the DSP Manager? Why it was removed?
[Nexus S Android Development] frank707:
Available on the download page as a separate download. Just preferred to make it optional.

Sent from my Nexus S
[Nexus S Android Development] frank707:
Should google wallet be packaged in the next release?

Sent from my Nexus S
[Nexus S Android Development] ranasrule:
is there a changelog for CM 7.1 ?
[Nexus S Android Development] sherlook1:
persian type problem

in all of version i have a persian type problem

when i type "پ" in text box after space the charachter changed to "~"
[Nexus S Android Development] rapperjk:
yes you should:)
[Nexus S Android Development] anremi:
http://cm-nightlies.appspot.com/?device=crespo
[Nexus S Android Development] frank707:
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
[Nexus S Android Development] sherlook1:
pleas solve persian problem

in all of version i have a persian type problem

when i type "پ" in text box after space the charachter changed to "~"
[Nexus S Android Development] alessandro_xda:
ok, it just happened using .50! after less than 2 hours fresh install (with wipe etc)
[Nexus S Android Development] bgoldie:
Yes please
[Nexus S Android Development] alessandro_xda:
it seems that when the phone locks, the battery is drained really fast!
[Nexus S Android Development] eiabea:
yes sry forgot to mention this ;) battery drains while phone is "dead"
[Nexus S Android Development] kuldaoo:
On original nightly 218 with default kernel my phone was "dead" too, it was the same like you are describing. I think this is a problem of nightly verisons. now I'm on 1.0.46 for two days and without the issue so far.
[Nexus S Android Development] Zisi911:
all this happened to me too but after 1.0.46 nothing happened yet. and another thing, except the alarm that doesn't ring also when somebody calls you to him it calls normally but the phone never rings and even after you take out battery and turn on phone there is no missed call no record at all of the calling
[Nexus S Android Development] Travis90x:
I used Theme Porter to port my Xeno Theme to your last ROM NSCollab 1.0.50! ;)

>>> Added Xeno Blu V11 for NSCollab 1.0.50<<<

___

Click to zoom

Hope you like it!

PS: I will be very glad if you add a link to my ROM in your first post, so you can use it as a "feature/theme"! ;)
[Nexus S Android Development] harisn:
Yes. Happens to me too!
[Nexus S Android Development] kevinngck1:
Are you guys using ondemand?
[Nexus S Android Development] mike216:
Use lazy I love faster and great battery life

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] mike216:
Frank this rom is awesome as always! Very glad you stayed with matrix!

Should we stay away from updating superuser in the market

I'm broke until Thursday (payday) buy I've got a nice donation for you to show my appreciation,Thanks my friend

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] kuldaoo:
I'm using smartassv2 or lazy
[Nexus S Android Development] mike216:
+1 lazy is very responsize and great! On battery

Lazy for governor sent from my nexus s/nscollab enter the matrix
[Nexus S Android Development] Ok_Kaleidoscope5109:
is there a reason why the Toggle 2G/3G option is grayed out when I want to add it to my list of notification bar widgets?

i'm on ver 50 also
[Nexus S Android Development] mike216:
I'm on 50 and its the same as the rest in widget buttons

Lazy for governor sent from my nexus s/nscollab enter the matrix