yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] chrlswltrs:
I guess that is the truth now with Obama eliminating our space program...

Sorry, I try to never say anything political but I couldn't resist that one.

Anyways... Downloading RC4 now. One of the commits I saw that I'm looking forward to is long press power widget opens the corresponding settings menu
[Nexus S Android Development] Hostile89:
It does seem quite speedy.
[Nexus S Android Development] Zenoran:
Freal what's the deal with 2 consecutive release candidates? Awfully strange.
[Nexus S Android Development] k4str0:
*WARNING* The 2g/3g notification widget toggle still causes the phone to implode. This will make your phone unusable, so make sure you nandroid before you test it. You have been warned!

There still seems to be this major bug even in RC4 on Nexus S.

How to replicate bug:

1. Enable the 2g/3g notification widget toggle and actually use the widget to toggle this network setting from 3g to 2g.

2. Reboot.

Welcome to your completely unusable Nexus S! :) You'll get a looping com.android.phone force close and no network. Only way to fix is to wipe your phone and lose all apps, save games, etc *OR* restore from nandroid.

Tested device:

T-Mobile Nexus S on CM7 RC4.

I'm just throwing this out there so its documented. Hoping it doesn't end up in the stable build.

*WARNING* The 2g/3g notification widget toggle still causes the phone to implode. This will make your phone unusable, so make sure you nandroid before you test it. You have been warned!

Edit:

Confirmed so far by the following users:

chasy, post #505 (http://xdaforums.com/showpost.php?p=12543417&postcount=505)

Hostile89, post #509 (http://xdaforums.com/showpost.php?p=12547489&postcount=509)
[Nexus S Android Development] dudeimgeorge:
Thank u so much for discussing about this concept. THIS HAPPENS ALL THE TIME. why can't they take out options that don't work??

Eg. 2/3g widget switch, lockscreen gesture for contacts, CPU clocking, camera zooming....
[Nexus S Android Development] zephiK:
its a RC/Beta/Nightly.. CM is a never-ending project, it will always have bugs. if this bothers you so much, go use stock
[Nexus S Android Development] Si_NZ:
Since I have a nandroid backup, I followed the steps to disable 3G and use 2G only, nothing happens after reboot...:confused:

I re-enabled 3G again just now.

I did wipe cache/dalvik before flashing RC4 though, not sure if that makes any difference.
[Nexus S Android Development] Hostile89:
Worked fine for me too.
[Nexus S Android Development] BrokenWall:
Even stock has its bugs, but they aren't as quick to fix them as the custom ROMs and on top of that the features are so much better with custom ROMs.
[Nexus S Android Development] zephiK:
Tell that to people who use their phones as phones and not as devices that are modified in every way possible. Stock has bugs but its the closest thing as purely stable for people who need to use their device as phones.

Either way. Don't complain about bugs when it isn't a final version. The CM team works on this for FREE, you can contribute to the CM Project if you wanted to yourself. So unless you're going to do it yourself, don't criticize about bugs being in a RC. It's a work in progress.

From a developer point of view. Removing these functionalities in the menu takes longer than actually fixing it. CM is always a work in progress. If bugs bother you so much, use stock or a ROM based on stock and come back to CM7 when the final version is released.
[Nexus S Android Development] k4str0:
You on T-mobile? I am with KB3 radio. Not sure if that makes a difference.

Edit:

This bug has been confirmed by:

chasy, post #505 (http://xdaforums.com/showpost.php?p=12543417&postcount=505)

Hostile89, post #509 (http://xdaforums.com/showpost.php?p=12547489&postcount=509)
[Nexus S Android Development] ryan562:
Rc4 works great for me so far. Love the new CM built-in CPU scaling/governor. Currently using it to overclock with Netarchy's latest kernel.
[Nexus S Android Development] swa2k4:
Same here it is ridiculously fast and overclocked its stable! No set cpu, in heaven!

Sent from my Nexus S running (CM7 RC4 and OC'd to 1.3ghz Netarchy 1.3.0.2 BLN. Monochrome themed)
[Nexus S Android Development] BrokenWall:
Lol sorry Zep I was not the one complaining in a few posts earlier, I was just making a comment, I know the bugs with custom ROMs like the one he is talking about with the EDGE/3G toggle. I just use Widgetsoid instead for my toggles since it sends you to the settings and I am all fine. I am a tweaker at heart. I know the problems that arise when Overclocking (I have a Phenom II x2 550 unlocked into a Quad @ 3.6Ghz) and I have worked hard to make it stable but sometimes it has its quirks and just crashes. Same with my phone, works great now that I found all my issues and worked around them.
[Nexus S Android Development] SubyWill:
Running perfect!!! even though I am getting the greyed out signal bars too.
[Nexus S Android Development] gavelis:
Had the greyed out Wifi and 3G icons also. My Google Talk icon in Launcher bar was away and my calendar was empty. So I thought it might help to reinstall the Google apps package. That fixed it! After Install (with Rom Manager) it asked me again for my account and everything is in sync again and the Wifi icon is green again...
[Nexus S Android Development] ogdobber:
sign out of talk then sign back in
[Nexus S Android Development] SubyWill:
I was never signed on. So, I signed off and then signed on and it's still doing it.

:(

It's getting really annoying too.
[Nexus S Android Development] gavelis:
As I already wrote in post #500 reinstalling Google Apps through Rom Manager solved the issues for me.
[Nexus S Android Development] daffyno:
whatsapp rings in quite mode too!

Can u fix pleaseeeee?
[Nexus S Android Development] chasy:
Yeah... crap.today i also experienced the 2g 3g switch Bug with the never ending fc of android.phone process.otherwise,awesome ROM ;D
[Nexus S Android Development] SubyWill:
Flashing the new gapps doesn't fix it for me. It's even worse than before now :(
[Nexus S Android Development] SubyWill:
Great, my signal bar is like this ALL the time now. -______________-
[Nexus S Android Development] phillevy:
I like the idea of setting cpu speed within the ROM, but like profiles in setcpu so this is making me reluctant to ditch it. What do people think?
[Nexus S Android Development] Hostile89:
Spoke too soon. I am getting the 2g/3g fc bug.
[Nexus S Android Development] jonjon68:
This has been my CM CPU settings visual since day one. All nightlies, RC's, any kernel. Portrait or Landscape. I've never been able to use CM7's CPU frequency settings.
[Nexus S Android Development] offenberg:
+1

I think the CPU settings is for the N1. It always worked for me on my N1, but never on my NS..
[Nexus S Android Development] aviramsegal:
off topic, where does your battery icon from ? is it honeybread ?
[Nexus S Android Development] phillevy:
Latest Netarchy kernel 1.3.0.2 fixes this.
[Nexus S Android Development] instigator008:
Lost only 4% battery overnight in 8 hours! Can't figure if its rc4 or the fact that I replaced launcher pro with spb launcher.
[Nexus S Android Development] Aria807:
Regarding the graying out of the signal and 3G/H, mine does it still on RC4. Generally was not an issue on the nightly #26. However it was a bit cloudy yesterday in Dallas; not sure if this really impacts reception to a point where our phone's signal bars would gray out or not.
[Nexus S Android Development] jonjon68:
With the mandatory vanity logo before the honeycomb boot animation and no way that I know how to remove it I have refused to use his kernels. Plus cm7 is unstable period or has been up to this point. Introducing non cm7 kernels has just been asking to bork up my phone.

I will go give it a shot since this is rc4 now but if the static morfic image is there before the animation its coming right back off after one random reboot or fc's.

Thanks for the info though.
[Nexus S Android Development] phillevy:
No intrusive logo's with the NS kernel - RC4 aside (not had it long enough), I do get the occasional bit of instability - but I put this down to always being on the cutting edge as well as overclocking, however mostly things are fine. I know I could go more stable but that would take away all the fun of tweaking:)
[Nexus S Android Development] bringonblink:
this was fixed in RC4
[Nexus S Android Development] netarchy:
Excuse me? I don't use any "vanity logo" with my builds, nor do I force any honeycomb boot animation, so I think posting this as a reply to a post regarding one of my builds is a bit mistaken.

I think you are confusing my kernel builds with honity.
[Nexus S Android Development] Arcarsenal:
+1 to this. Netarchy's kernels are some of the purest, most stable and least flashy out there. No extra boot animations or graphics. I use them exclusively for that reason. And - not to be a suck up, it also has excellent dev support.

edit: more on topic. Almost missed my alarm this morning with RC4. I noticed that Gentle Alarm would FC every time I tried to load it, and I guess that killed the alarm service sometime overnight. Shortly after that I wasn't able to open settings without a constant FC of the settings app. I wiped dalvik with root explorer and reflashed RC4 and Netarchy 1.3.0.2 and I seem to be okay now. Anyone else see something similar with FCs of Settings or other apps?
[Nexus S Android Development] Aria807:
not that I can tell. I wiped my phone and flashed RC4. I didn't wipe my SDcard tho. So far no Force Close problems.

I did notice that my market did try to reinstall all the previous apps I had b4. I guess it's a new feature? I'd still use titanium tho because it restores my settings as well.

Also to be safe when flashing a new rom, if I decide to go the wiping route, should I also wipe my SD portion?
[Nexus S Android Development] maltloaf:
I have flashed this today for the first time and am using it together with Netarchy's 1.3.0.2 CFS kernel. So far I have had no issues whatsoever and the phone feels lightning fast.

I came from stock 2.3.3 (although rooted and using the above kernel for overclockability and CIFS)
[Nexus S Android Development] sloppy1:
???????????????

rc4 with ogs 1.4.7 kernal full wipe done data n cashes but still losing net and call signals
[Nexus S Android Development] JUSMEJOSE:
everything is working perfect geaaah!!
[Nexus S Android Development] lavcoles:
edit......
[Nexus S Android Development] jonjon68:
You are correct sir. Apologies.
[Nexus S Android Development] johnkim0011:
First time installing custom ROM..

I currently have stock 2.3.3 ROM and Netarchy 1.3.0.2 CFS and would like to flash CyanogenMod 7 RC 4 ROM.

I downloaded RC 4 but which Google App file am I downloading from the below link?

http://goo-inside.me/gapps/

So I copy both CynaogenMod RC4.zip and Google App.zip file to SNS root.. then..

After I flash RC 4 on CWM via recovery [after it has been completed], I should flash [install] Google Apps via recovery before rebooting SNS?

So it will wipe everything right? Do I install back root apps like Superuser, ROM Manager Premium, RootExplorer, etc.. like it will work like my current setting since it's already rooted?
[Nexus S Android Development] phrag:
camera flash

The camera flash has stopped working (options to turn on are greyed out), however flash works in video camera mode...

any idea's?

thanks in advance
[Nexus S Android Development] Aria807:
anyone know why the reception keeps graying out? I'm not losing connection but it keeps graying out everytime i unlock the phone then it turns back to normal again.
[Nexus S Android Development] Five0nIt:
i think re flashing the gapps fixes it.
[Nexus S Android Development] fosdos4790:
Open the camera click on settings on the far right and make sure your scene mode is set to auto.
[Nexus S Android Development] jonjon68:
CM7 is rooted out of the box.

Don't think it will wipe itself, not sure, but you need to wipe data, wipe cache, and I wipe dalvik cache and fix permissions just to be sure.

Then flash CM7 zip, then yeah, I always flash google apps after CM and before I bounce the phone.

As far as apps, a lot of people use titanium. I use mybackup pro but these days I only restore data (phone settings and application data only) usually. I let google back up and restore my apps then restore the data to the apps and phone home settings to get my folders back.

Oh, you will lose your custom kernel when you flash CM7 but you can flash it back over the top. Probably doesn't matter but I do actually let the phone boot once with default CM, give it time to restore things etc.. then go back in to recovery and flash the custom kernel. Custom kernels have added to the instability CM7 has caused for my phones to be worse but I'm on RC4 and Netarchy's latest right now and have been ok for 24 hours or so.
[Nexus S Android Development] co0kie:
I must say, I'm a Nexus S owner and the only reason I finally feel like I can enjoy my Android phone is solely because of your SUPER STABLE KERNEL - not even one crash since i've started using your ROMS and its been super fast. Thank you.
[Nexus S Android Development] bajansurfer:
I had this problem before. Try wiping the data for the camera app. Manage apps > all > camera > clear data.
[Nexus S Android Development] phrag:
awesome, was on night mode for some reason!

thank you for the fix, much appreciated =)
[Nexus S Android Development] phrag:
CM7 RC4 awesome so far!

Thank you so much for all your great work :)
[Nexus S Android Development] bringonblink:
Are folders working for everyone? As in homepage folders you create
[Nexus S Android Development] fosdos4790:
No problem. Glad I could help.
[Nexus S Android Development] YDardeer:
RC4 browser seems ALOT smoother and faster, or is just a placebo effect. RC2 wasn't cyanogen's best work imho
[Nexus S Android Development] jonjon68:
Frankly CM7, at least on the NS, has me questioning the work in general.....in my opinion. Here we are at RC4, very close to release, and I got two phone meltdowns today. One from using the camera, just using it. Froze and bounced. This was a problem what? Two months ago almost? Then just a random reboot when I was listening to music.

I've just come to grips with, I hope anyway, that this phone may just be a POS. Not mine specifically. Nexus S. Which is pretty easy to buy since it's a Samsung. I say hope because at least I can resolve that one.

I wonder what other phones are experiencing on CM7.
[Nexus S Android Development] generalagony:
I for one will not be buying anymore Samsung phones. I love my NS but there are just too many hardware quirks that are unacceptable for a $530 piece of equipment. CM supports so many other phones that I am confident I will not need a Nexus device in the future to get the most up to date releases by the CM team.
[Nexus S Android Development] zephiK:
good luck with customized kernels.. you'll have to wait for 2.3 kernel source to be released by HTC/whatever

I personally haven't experienced ONE problem with the phone yet. Maybe a occasional reboot but that was pre 2.3.3.
[Nexus S Android Development] ryan562:
x2. Rc4 has been running great for me.
[Nexus S Android Development] fixedonfixies:
It took me 5mins of use to realise how much I love this rom. Soooo much useful flexibility. and am thinking of posting a video on some ways I have put some of the flebilities to excellent use.

But quick question, what sequence is best for the most stable flash?

I initially flashed netarchy on a clean slate then CM7 but afterwards Netarchy wasnt showing up in my kernel version.

So I tried flashing CM7 on a clean state then afterwards flashing CM7 and with this method Netarchy showed up but i get a black screen on boot up no "Beautiful " Cyanogen animation :( am not so bothered since the roms is been so stable I almost have no use to reboot, but illd like to know the appropriate sequence on flashing the kernel.
[Nexus S Android Development] zephiK:
You need to flash the KERNEL after flashing CM7. Upon flashing CM7, it overrides your kernel with the stock kernel.

I'd recommend doing: Wipe Dalvik, Cache, Flash CM7, Flash Kernel, Reboot

it'll take longer than usual on the first boot because dalvik and cache was wiped, but it'll boot.. give it time, its only slow on the first time.

(Dalvik, Cache wiping is optional but its better to do it)

When you update your ROM to a newer nightly. You have to reflash Netarchy's kernel again.

The phone itself doesn't have a problem. It's just the user's lack of knowledge of properly flashing and debugging their phone. It's kinda like Windows, if you don't run antivirus and don't care about your system... problems will arise. But if you maintain it well, your phone/PC will treat you back with the same respect and run at its full speed.
[Nexus S Android Development] BrokenWall:
RC4 (w/ Netarchy 1.3.0.2 @ 1.3Ghz Ondemand) has been great to me so far, I have had my phone running for a total of 60 hours straight with alot of usage. Here is a battery shot of one day when I used the phone and was texting alot and sending emails.

(I was trying to get info on a new car loan and call a tow service, my wife's car is knocking a piston rod, hense alot of phone usage)

By the way that is 1:07am as in after the day was over done and over.
[Nexus S Android Development] fixedonfixies:
Thanks man, really appreciate the break down. I Concur on that last paragraph. I've treated this bad boy right and it's sure doing me right except am not very clear on kernels. But am fine now.
[Nexus S Android Development] zephiK:
You could google and wiki what a kernel is. If you're going to try a kernel, I'd recommend using Netarchy's 1.0.3.0 (or 1.0.3.2). It offers a lot of features, check out his forum thread. Some of the major features are: Voodoo Color, Voodoo Sound, improved battery life (varies between user).

Trust me, its relatively easy to do and it's worth it!
[Nexus S Android Development] jonjon68:
Must be nice. But if you look through the CM threads on this phone you will see pretty clearly you are in the minority.

That is however a small silver lining. At least circumstantial, anecdotal evidence CM7 hasn't lost it's mojo. Look forward to ending the Samsung trainwreck, as soon at HTC comes out with something I want, or giving LG or Motorola a shot if there's something juicy.

I had hoped CM would end the misery of the Galaxy phones and Android. I think what it may have confirmed for me is, I'm a sucker for giving them another shot.
[Nexus S Android Development] zephiK:
The majority? I use new nightlies on a daily basis and never experience any bugs. The Nexus S can't even be compared to a Galaxy S. It has none of its attributes with exception to Odin but that isn't even popular on the Nexus S.

Anyway, if you want to flame "Samsung" take it elsewhere. CM7 for Galaxy S isn't supported and all the releases for that are unofficial builds.

Have fun with HTC's attempt to lock down custom ROMs etc.

I personally don't see a problem with Samsung whatsoever.

Plastic backing? Whatever. the phone isn't cheaply made, its no where close to cheap.

Everybody will have complaints about a manufacturer.

HTC: Cheap speaker, etc.

Motorola: Bootloader, Motoblur

Samsung: Backcover, Lack of updates, TouchWiz

Sony: Not releasing any updates

.. move on already :|

CM7 + Nexus S is perfectly fine. if somethings not functioning properly then you need to start from scratch and wipe dalvik/cache/factory.
[Nexus S Android Development] Aria807:
Damn went to movies tonight. After movies, took my phone out and it was dim bootlooping.
[Nexus S Android Development] mred-it:
Try this:

adb shell

cd /data/data/com.android.providers.settings/databases

sqlite3 settings.db

Then enter:

delete from secure where name like '%prefered%network%";

delete from secure where name like '%cdma%";

Take from:

http://code.google.com/p/cyanogenmo...=ID Type Status Priority Device Owner Summary
[Nexus S Android Development] brownmonkey:
I am running RC2 at the moment and i havent had any problems really apart from occasional reboot. I am thinking of upgrading to RC4, but was just wondering what the procedure is for me to upgrade..

Can i just flash the new rom without having to wipe any data, cache or dalvik cache? Also if i do this, will i lose gapps or any other apps i have installed?

and so will i have to use titanium backup to restore these apps?

is it similar to doing a stock update, where by it just works and all the apps you had installed before are still there? or is the upgrade like flashing a completely new rom where by you have to restore the apps from titanium?

thanks in advance.
[Nexus S Android Development] AndyCr15:
RC2 seemed the most stable for me to be honest. I could go days without boot loop or crashes. Now I seem to get around 1 a day :(

Also, did someone have a fix for Launcher Pro FC on restart? (and random times through the day)
[Nexus S Android Development] phillevy:
LP has always done this for me on restart and I've just put up with it - would love a fix!
[Nexus S Android Development] Bandis710:
I had the same problem, but for me the problem was solved by going to LP preferences/general and then tick the option keep in memory + going to settings /cyanogenmod settings/performance and there tick lock home in memory ..
[Nexus S Android Development] jonjon68:
Nah, I'll stay. Don't need advice but like all here, you're entitled to your opinion and expressing it, which is what it is, just like mine. Have a great day buddy. As long as I have this phone I'll be around. Deal.
[Nexus S Android Development] jonjon68:
Nope, it's the phone. It's the Vendor actually. The NS at least has CM to help make it easier to stomach.
[Nexus S Android Development] jonjon68:
+1

Exactly. Careful though. The Samsung loyalists might open a can on ya. Well, a lame attempt to anyway. ;)
[Nexus S Android Development] jonjon68:
Yep, I was thinking of the Morfic boot image. Apologized, thanked and donated to Netarchy. Using his latest right now. Really impossible to tell if it aids in the typical Samsung/2.3 dumbfuckery, but I don't think it makes it any worse.
[Nexus S Android Development] gasparzim:
Installed the v7 yesterday, so far so good, no random reboots.

But last night, I turned the phone off, and when I booted this morning, some widgets are not working, like simi clock and droidstats. First, they show a "error loading widget", and after a reboot, they look like the screenshots attached.

What could be causing it?
[Nexus S Android Development] Hostile89:
Thanks, I have not been using the 2g power widget since. Maybe later I will do a nandroid and see if it works.
[Nexus S Android Development] zephiK:
Stop being so afraid. You download rc4 go into clockwork and flash rc4 its that simple. Flash a custom kernel over it if you used one. I'd recommend wiping cache and. Dalvik.

Wiping factory is the only one who would wipe your settings and apps.

@jon: kind of a useless response but whatever. Deep down your heart you unconditionally love the NS ;)
[Nexus S Android Development] :
I believe you are using launcher pro? If so, it can do that sometimes, just reload the widgets and everything should be fine on your reboot and every one after that.

-I wrangled together some consonants and vowels and created this post-