yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ogdobber:
that is disapointing:(

It seems that the majority of people not having problems are running another kernel??? Am I right on this?

I am for sure running my 1.4.7 and have have no issues (besides the known 2g/3g widget, etc)

My battery life too has never been better! moderate to heavy use I have 50% after 14 hours...
[Nexus S Android Development] jerrycycle:
+1 to this.
[Nexus S Android Development] jonjon68:
Heavy use is not created equal. I do seem to be getting better battery life on final though. I don't have to plug in now until 2 or 3 pm which is not a trivial delta. Previously it was by noon typically.

Oh and I didn't get a backlight crash until I started using a non cm kernel. Netarchy's. But it's rare and I can live with it so far. Worth it for OC and voodoo.
[Nexus S Android Development] NPS_CA:
I'm also frustrated with this. I've had ZERO ability to capture KMSG's or the last_kmsg of the behaviour I've seen... I would love to setup a proper kernel debug environment or get a debug version of the kernel as I'm NOT able to get any constructive failure info on stock kernel. Bottom line for me is CM7 with stock kernel is unusable (not complaining to CM dev's) I have to use netarchy's kernel which is near solid although I get a random bootloop every few days. Frustrated with this and frustrated that others have solid performance. I'm wondering if some HW diff or rev code of the hw/devices is causing some of us to see this and other to not. My bug got marked stale as well which is another frustration: http://code.google.com/p/cyanogenmod/issues/detail?id=3436

On the last_kmsg. I've even run: adb shell dmesg however it catches nothing when the hang happens :) Would love to know if this phone has jtag/serial for pushing out debug without ADB (seems ADB/dmesg isn't catching this failure)

Also regarding the dev frustration: I've been here since G1 then to the N1 and now on the NS ; the only reason I moved to the NS is my N1 died (****ty HTC warranty support); my HTC frustration drove me to Samsung (which I may regret). What I don't regret is working with the dev's and those who contribute to make CM bulletproof on multiple devices. I'm NOT timid to file a bug (on issues that I can generally repeat) instead of whining here - I'm also not bothered to dump logcat's, kmsg logs or other things to help the dev's out. We're moving 100 times quicker then any inside OEM dev team!
[Nexus S Android Development] sufibravo:
Amen to that!!!
[Nexus S Android Development] Si_NZ:
I've also had a black screen with touch buttons lit problem with CM7 final + James Bond kernel 1.4.7. I can't remember whether it started bootlooping soon after or if it was sometime later after a battery pull.

I didn't do oem lock + unlock as I have 10GB of stuff on the SD card, I don't want to copy all that again, takes too long. However, I did wipe data/dalvik and formatted system/cache/data before installing CM7 final.

While it was bootlooping, I can only see something is segfaulting in logcat, I'm attaching the logcat output if it helps.
[Nexus S Android Development] Bronk93:
On the last nightly and this v7 I'm having a data issue. When trying to access the web my phone will switch between 3g/H a few times the get stuck on 3g but never pull up a page. A reboot is the only way to remedy it. I did a full wipe when I installed, anyone else having this issue?
[Nexus S Android Development] mortal300:
Still same problem with the G/3g flipping and then turning grey. When phone is locked it looks great all green and good. Then u unlock and open gchat and it opens as if the whole time its been losing connection and the green bars at the top are just fooling you -_-

Idk what to do :/
[Nexus S Android Development] Aria807:
Yarr. having this issue ever since RC3.
[Nexus S Android Development] ogdobber:
what are you apn settings? and when you are on wifi is it set to never sleep? I suspect that when your phone turns off, the wifi sleeps turning on the 3g then maybe a problem with the apn settings...

makes sense and is the only thing I can think of
[Nexus S Android Development] Bolick:
Unfortunately I tried your kernel 1.4.7 while being on CM7 RC4 and got bootloop once. That might have been caused by some crap left from RC2 and RC3 I tried before. BTW if your kernel only differs from CM stock with Voodoo and BLN do you think these two additions might fix stock kernel issues? Just wondering.

And also, how often do you reboot your device? I mean it's amazing if you have uptime say more than a week without issues. As for me it feels like if I reboot device daily there would be no issues, which is definitely a way, but not so convenient.

Speaking about hardware roots of problem described... well, I'm quite sure that it's not a point here. Because I spent a week with true stock 2.3.3 and got nothing to complain.

Anyway I'm here not to blame anybody but to solve problems, so I'll be happy to find out the solution for stable system.

Cheers
[Nexus S Android Development] stennett:
Just about to install my first ROM and seems as CM is so highly thought of by so many xda users I have decided to jump on the band wagon.

However I have a few noob question's:

1) what date do I need to wipe?

2)will it wipe external storage (sd card)?

3)what data will I loose when follwing the instalation instructions. (Need to know so I can ovbiously back that data up so I can restore after instaltion.

Thanks in advance to anyone who helps.

Edit: Forgot to add, I'm rooted and have rom manager, Clockwork Mod installed allready.
[Nexus S Android Development] reddv1:
Anyone notice the gallery being choppy when scrolling through an album or pinching to zoom? It feels very choppy to compared to RC4
[Nexus S Android Development] damngood98:
i would wipe everything installing your first rom. wipe data/factory reset, wipe cache, go to advanced menu and wipe dalvik cache. the good thing about cm though is that there aren't too reasons you're going to have to do this again unless you run into problems that are unique to you and not to others. i haven't wiped my phone since switching to cm.

it won't wipe your external but always a good idea to back it up just in case.

data loss? it'll be like turning your phone on the 1st day you got it. you'll have to log into gmail, redownload all of your apps,etc. that's assuming you flash gapps to. don't forget about that.

if you want a kernel check my sign and look for it on the main developement page. it allows overclocking. i'd check out voodoo control app in the market if you decide to use it. and if you want a good app for backing up just about everything try titanium backup. it's worth getting the paid version. i wouldn't recommend using it for backing up system apps but it's great for market stuff.

good luck!
[Nexus S Android Development] stennett:
Thanks for the quick reply, will I need to flash clockworkmod and superuser after flashing the ROM?
[Nexus S Android Development] damngood98:
you should flash clockwork first using rom manager. it's in the market. open the app and you can flash the recovery through the app. superuser is in the market too if you don't have it already.
[Nexus S Android Development] albertogg:
I've been using CM7 nightly #39 because the CM7 final notification bar bug was really annoying me, but I must say that with the last og kernel, 1.4.7.2 the phone is working better than ever... so far 50 hours uptime no boot loops or weird things.. I really recommend it.
[Nexus S Android Development] stennett:
Is there away to use the standard launcher insted of ADW ?

Thanks for the help just flashed my first sucessful ROM!
[Nexus S Android Development] kemsiro:
get the stock launcher launcher2.apk and adb push
[Nexus S Android Development] dudeimgeorge:
og, im not bashing cm7, at all, im addicted to its brilliance.

i just like bringing up these issues for awareness. i still stick to it. yeah i guess im being an ass when i question the principle of a 'stable release' and have options that are available to use, not work. again, its about bringing it out in the open, all to make it better. i also talk with excessive emotion on the forum, just for more colorful reading i guess.

also for everyone to know. netarchy + latest stable CM7 + sdcard speed enhancment = no loops, fast action.
[Nexus S Android Development] steve.garon:
I'm a bit curious about the sd card enhancement. Can you precise? I've use the app sd increase on the market but that doesnt seem to do anything. Benchmarks are the same and no noticeable speed increase while using the phone. Is there another sd card trick I should know about?

Ps: running cm7 stable with netarchy 1.3.0.2 bfs

Steve
[Nexus S Android Development] AllGamer:
How long is the initial boot the first time CM7 is installed?

it's been like 5 min already, and it still is playing the animated CM7 logo on the skateboard

i wiped data / cache

i wiped battery stats

i wiped davilk

i tried flashing it again

just CM7 + GAPP, lets see how long it takes now
[Nexus S Android Development] mortal300:
Wifi sleep policy is set to never. APN setting is T-Mobile US (epc.tmobile.com), Mobile data is obviously checked on

** Last night the phone was on normal 3G all night. I went to bed with it green. I woke up with it also green and noticed I did not have emails which is VERY odd. I opened my phone opened GChat and bam it went to grey. After rebooting GChat and resyncing, all the sudden all my emails synced and came through. Emails form 1-2am and 6am all came in when I woke up at 10am -_-
[Nexus S Android Development] AllGamer:
hmm... it's been over 10 min already, still not booting into the OS

there is something wrong with CM7 7.0.0

going back to SuperAOSP
[Nexus S Android Development] DinarQ8:
When I change theme power control in bar hide
[Nexus S Android Development] KidCold:
Yeah..... this didn't happen to me. Booted up in the standard time
[Nexus S Android Development] AllGamer:
any idea what else i can try to make CM7 work on my phone?
[Nexus S Android Development] zephiK:
You wipe factory settings? Verified md5 hash?
[Nexus S Android Development] KidCold:
Factory settings wipe?

Maybe try flash Cm7 first then on reboot go flash gapps after that?
[Nexus S Android Development] AllGamer:
http://xdaforums.com/showpost.php?p=12930880&postcount=826

that's the first thing you do when you change ROM

any other ideas?
[Nexus S Android Development] zephiK:
You said data / cache :P

Verify it's md5 hash.

Are you applying a custom kernel over it? If you aren't, try netarchys kernel and see if that would do anything. Or even do a logcat on seeing what's wrong with booting.
[Nexus S Android Development] ogdobber:
fastboot oem lock/unlock

seems that certain things are sticking and clockwork doesn't seem to clear everything properly. the lock/unlock has worked for most...
[Nexus S Android Development] ogdobber:
specific epc.tmobile settings??

can you do a logcat with the phone idling? (after at least 1 hour after boot)
[Nexus S Android Development] secure-web:
status 7 error

Install per ADB the new Clockwork Vers. :3.0.2.4 the 3.0.0.5 it`s buggy :D
[Nexus S Android Development] smoothfreeze:
Still getting no 3G/H on CM7 (white bars). However I can surf the browser to sites like google, facebook etc. But whenever I want to sync my google acc, I will get a network error. Wtf? Another thing, after flashing to CM7, my build number changed to GRI40 instead of GRI54 in the settings on stock. Maybe that is the problem?:confused:

Back to stock for now, where I can get 3G.
[Nexus S Android Development] zephiK:
GRI40: America 2.3.3

GRI54: Europe 2.3.3

It shouldn't matter though. What radio are you using?
[Nexus S Android Development] ogdobber:
GRI54 is also the 9020a...but the euro radio is better (faster speeds, same connectivity)

cm is GRI40 but it doesn't matter runs fine on my 9020a
[Nexus S Android Development] zephiK:
yeah agreed... KB3 is the euro radio
[Nexus S Android Development] smoothfreeze:
My radio is I9023XXKB3. If it doesn't matter, I wonder what's wrong with my installation of CM7...
[Nexus S Android Development] Xene55:
Hmm, I'm on:

I9020XXJK8

GRI40

Should I be flashing something else as I am in the UK? I flashed many a radio file on my Desire - same process on Nexus S?

A slight oddity is when I select shutdown from the tray menu then try and turn it back on again. It looks as though it gets stuck on a black screen on boot with just the backlights on behind the four buttons (they get brighter if you hold your finger over them). If you leave it for long enough it does eventually respond but it looks broken. Maybe something to do with the SIM lock I have setup? Not sure what happens for other people.
[Nexus S Android Development] Haizum74:
Ok mine went to black screen over night, reinstalled and nothing, wont boot at all. Bugger!

EDIT Ignorre, put wrong kernel on, oops
[Nexus S Android Development] stennett:
Can anyone point me in the right direction, I need instructions on how to keep cm7 but run stock launcher.

Thanks in advance.
[Nexus S Android Development] Haizum74:
Anyone had trouble getting wifi working? Just done a fresh reinstall and now wont obtain IP address.
[Nexus S Android Development] Xene55:
Woo! On I9023XXKB3 now. Kernel next. FINGER LICKIN' GOOD
[Nexus S Android Development] jamallj:
got random reboot here.. but not stuck on load screen upon reboot.. need to pull off the battery and manual reboot.. one more strange thing.. after reboot fb application is disconnected.. means no username orr password stored and need to re-login.. anyone facing the same problems?..
[Nexus S Android Development] XxSilent22xX:
I have had the same issue, I had to wipe dalvik cache reflash rom and wipe facebook and that fixed it.

Sent from my Nexus S
[Nexus S Android Development] omegacell:
I have two Nexus S units running CM7 w/ Netarchy BLN CFS and one is getting really good battery life, the other is terrible. Looking at battery usage stats, one unit is reporting 25-40% usage from the Gallery application (WTF?). There aren't even any pictures on the phone and the gallery is never being used! Any suggestions?
[Nexus S Android Development] zephiK:
restart all over.

fastboot oem lock

then fastboot oem unlock it

wipe factory,cache,dalvik

reflash

... and wipe battery stats (recalibrate your battery. google the steps to properly do it)
[Nexus S Android Development] i.peteycent:
What's the purpose of wiping factory, cahche, and dalvik after an OEM lock unlock?

They are recommended when upgrading from previous versions without the OEM step.
[Nexus S Android Development] jerrycycle:
I deleted the stock gallary and use quickpic from the market in its place
[Nexus S Android Development] omegacell:
How do I delete it?
[Nexus S Android Development] jerrycycle:
Use titanium to freeze it if you ever want to use it again. Titanium can be used to delete it all together.
[Nexus S Android Development] zephiK:
What's the purpose of not doing it anyway? Better safe than sorry.
[Nexus S Android Development] i.peteycent:
Because its not needed. An OEM lock unlock completely wipes everything, already. That's the purpose for not doing it.

Wiping an already blank phone makes it extra safe... good one.
[Nexus S Android Development] zephiK:
If it's already wiped and you rewipe it, you're not losing anything. It roughly takes <10 seconds to do this.

As I repeat again:

What's the purpose of not doing it anyway? Better safe than sorry.
[Nexus S Android Development] sushiboy:
I had the same issue. I tried fasboot oem lock/unlock, but it didn't help. CM7+Netarchy kernel (NSCollab-1.0.18) solves my problem.
[Nexus S Android Development] i.peteycent:
As I'll repeat again:

Unnecessary
[Nexus S Android Development] jonjon68:
Agreed. The question was "what's the point of not doing something that's completely unnecessary". Paraphrasing but it seems like a rhetorical question to me. The answer is, well should be, obvious.

Using the logic in the rebuttal, lets do it twice. It'll only take 20 seconds. lol
[Nexus S Android Development] KryPTiCk0d3:
I run into that same problem, I deleted Gallery, then went back to battery stats and com.cooliris.media was in it's place, was unable to find this and delete it. wtf.

I found another thread that says to go to accounts and sync and under your account options disable sync to picasa. So I did that and it did drop gallery battery usage to under screen.

I couldn't find any trace of Gallery actually running, it wasn't listed in running apps or processes.. and I got 14 hours of battery life yesterday before I went to bed it still had 30% left, after messin with it all day.

So is it lying?

Oh and a wipe didn't help.
[Nexus S Android Development] zephiK:
What's the point of NOT doing it though? If it doesn't "do anything" but you do it anyways. What's the damage thats being inflicted? Exactly.. nothing.

It's a simple task and takes <10 seconds to do. Some people prefer having the feeling of wiping it as a measure incase for some reason the phone didn't wipe it.

Either way, if you want to have this debate inbox me. Don't want this thread to go out of topic.

Not having any problems with gallery. Although I do get this pretty annoying bug where 5 folders would display. 2 folders would appear on the first column and im unable to click on the 3rd (or 4th, 5th) folder thats on the second column. Workaround is to press on first or second folder, press back and then they align properly.
[Nexus S Android Development] ksweat2292:
lol
[Nexus S Android Development] Darrien13:
On the notification bar you know how it says what service you are on edge or 3G well I'm having an issue on CM7 when I'm on 3G it says H at the top and sometimes it glitches up and says 3G at the top for a slight second. Anyone else have this issue? Is it normal thanks. It also occurs sometimes on the MIUI rom also.
[Nexus S Android Development] omegacell:
Yes a total wipe and redo made no difference to me to I deleted Gallery with Titanium backup and then I went into the /Android folder and deleted any folders to do with com.cooloris.media. Now it's not draining my battery but I also don't have the Gallery app..
[Nexus S Android Development] jonjon68:
Also unnecessary. Nothing to debate.
[Nexus S Android Development] zephiK:
Great way to take out the rest of my post. It was unnecessary for you to quote me and to post that. Unless you have something to say towards CM 7.0.0-FINAL don't get off topic.

@Darrien: H is HSDPA which is 3.5G. I don't think it has anything to do with the ROM. It just means that you're in a area that has weak HSDPA and it's toggling between 3G and HSDPA (3.5G). In your signature, I see that you're using a older version of Netarchy's kernel. You could possibly try updating it to either 1.3.0.0 or 1.3.0.2. I recommend 1.3.0.2 since it has a newer version of Voodoo Sound. And it's pretty stable, haven't experienced any problems with it yet.

If it still occurs on 1.3.0.0/1.3.0.2 try the CFS version of it.
[Nexus S Android Development] dbairduk:
I am finding this worse than RC2 to be honest. My alarm failed this morning and had 2 random re-boots requiring removal of the battery.

Also I couldn't answer my phone earlier had to use the power button to turn the screen on and off to answer it.
[Nexus S Android Development] hayabbusa:
probably the worsed cm7 build ever!! cant use the phone due the com.android.phone crashes, adw crashes also..

do something
[Nexus S Android Development] Aria807:
Weird I'm not experiencing any of those FC problems so far. I think when I 1st flashed RC4, it did a dim bootloop once, but I havn't seen it again and my phone's got an uptime of 122 hours so far. I think only issue that still remains is my 3G/H/Reception keeps randomly graying out every time I unlock my phone, though no reception is actually lost. Just a cosmetic annoyance for me.
[Nexus S Android Development] ogdobber:
how "clean" was your install...i.e. what was wiped? and what were you coming from?
[Nexus S Android Development] hayabbusa:
wiped everything what is possible, comming from stock 2.3.3, just rooted nexus s
[Nexus S Android Development] ogdobber:
can you expand on that? did you flash from recovery or use rom manager? what exactly did you wipe? data/factory reset? cache partition? dalvik cache? battery stats?

that would be everything possible...
[Nexus S Android Development] Bolick:
Hi ogdobber,

just looked into my phone info and was quite surprised: 120 hours uptime with no issues at all.

I guess the reason is Netarchy kernel I flashed last week. And since flashing no reboots.

It is 1.3.0.2-CFS version (2.6.35-11-netarchy-nexus-1.3.0.2-cfs-natas).

So I think your assumption about CM7 stock kernel problem is quite close to reality, while you are saying there're no issues with your kernel and I see no problems with Netarchy's one.

Now I'm curious what is a difference that causes instability of stock CM kernel.
[Nexus S Android Development] zephiK:
theres no such thing as "stock CM kernel" the kernel being flashed upon flashing CM7 is the stock NS kernel made by Google. You can verify this by:

1) Flashing CM7

2) Boot

3) Use SetCPU or even go to "About Phone" it'll say that its signed by google.
[Nexus S Android Development] Kiralina:
Had some FC's with CM7 and the default kernel, but since I flashed Jame Bond triple dub all works smooth and very fast and had no FC's at all.
[Nexus S Android Development] KidCold:
I also had problems when using the default kernel. After changing to netarchy everything has been perfect. Anyone who is having problems I urge you guys to flash a different kernel and see how that goes.
[Nexus S Android Development] NPS_CA:
Funny that 2.3 STOCK Google provided official ROM results in 96+ hours no issues seen up to that time.

CM7 with it's default Kernel; less than 5 hours of run time

CM7 + Netarchy kernerl: Over 48 hours + of runtime. Right now actually on 4 days of running OK (but avg is 48 hours)
[Nexus S Android Development] hayabbusa:
yes, all that was wiped. istalled from recovery. was working ok for a day, and then just started.

now back to rooted stock and happy again :)
[Nexus S Android Development] konman795:
I usually don't complain because Cyanogen is freaking awesome but I've gotten the "com.android.phone" force close 4 times and have had to completely wipe and reflash 4 times too since I've flashed the "stable" final release. Please fix this!
[Nexus S Android Development] zephiK:
update to nightly #41.. the so-called "stable" version is simply a nightly given another name.
[Nexus S Android Development] jpalo:
I'm getting random restarts few times a week with CM7 stable and netarchy 1.3.0.2 cfs. Some of these restarts (maybe 25%) end up in weird state when CM7 boot animation is spinning, but colors are somehow inverted, and it never proceeds past that boot animation.

Yesterday, when getting a call, phone restarted and went into boot loop (first boot lop in fact). There, boot animation colors were fine.

I did wipe everything when coming from 2.3.3 stock unrooted to CM7 RC4 (where this issue was also present), and then upgraded to CM7 final, and also installed netarchy. Didn't wipe or anything when going from RC4 to stable.
[Nexus S Android Development] tadaha:
hmmm, com.android.phone crash is probably from the known 2G/3G toggle bug.

this bug has been around for the Nexus CM7 since the first few nightlies.

Well, simply do not use the 2g/3g toggle in either the notification power widget, or in homescreen power widget.

Also, if u r using the data toggle widget, do not select the "Data disable/enable 3G" option. Basically anything in the power widget which toggles between 2G/3G will cause the phone to go into a infinite com.android.phone FC loop, and the only way to fix it is to do data wipe (factory reset) in CWM recovery.

BUT you can manually go into settings -> wireless & networks -> mobile networks to select 'Use only 2G networks' It's troublesome, but other than this bug, for everything else that this awesome CM7 offers, it's more than worth it.