yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] zephiK:
search street view on the market and download the app
[Nexus S Android Development] konman795:
I love cyanogen
[Nexus S Android Development] steve.garon:
I'm not sure if this is intended behavior or not but sometime the 3G/H icon show up transferring data while on wifi. My impressions where that cell data was disabled on wifi?!

I'm also suspecting some apps are always using the 3g even when wifi is connected since my data usage per day climb up quite a lot since I switched from N1 to NS 4 days ago.

Anyone else?
[Nexus S Android Development] YDardeer:
CM7 is the worst ever. Previous RCs were much more stable

- phone freezes almost two times a day

- veeeeerrrrry sluggish. Its even worse ever day

- phone lasts only 10 hours on battery. Maps keeps working in the background according to Battery Status from the settings menu. Its eating 26-30 percent of the battery. Force stopping the app doesn't seem to help as Maps just starts again. Had to uninstall it.

- went late to work today because the alarm didn't run. When I woke up found the boot animation loop.

All in all very terrible experience. And I wiped/factory reset everything.
[Nexus S Android Development] liorry:
It's going to sound ungrateful so I'll first say I really appreciate CM team's work and even donated.

IMHO - CM7 for NS, since the beginning, is the worst ROM for NS at the moment.

There are much better AOSP builds out there, and even stock ROMs.

I have tested every ROM in this forum, including MIUI and I've never encountered problems with any of them like I got using CM7 (tested almost every nightly... the most stable one was 36 and then it went bad again).

All the issues you were stating are there from the beginning... I bet your boot loop was with a dark screen right?

I would love to use CM7 because of all its features but right now this is just a bad ROM... I guess it's because they build for sooooo many devices or maybe it's because NS/Android 2.3.3 ... don't know..

Again, the team is great and its work is greatly appreciate even if sometimes there are problems...
[Nexus S Android Development] ogdobber:
both of you are doing something wrong. CM7 is the best rom I have EVER used.

I have not had a reboot since 2.3.2 and I am getting unbelievable battery life (yesterday, normal to heavy use, I had 50% battery after 14 hours)

There is ONE problem with CM7 and that is the 2g/3g power widget DO NOT USE IT! to change to 2g go to settings/wireless&networks/Mobile networks/use only 2g networks

dardeer- maps tends to use battery if due to latitude so check the settings, also turn off the gps. many apps use your location to better serve, and if your gps is on, then that much more battery will be used to do so.

also signal strength significantly affects battery life. If you have 4 bars of 3g then no problem, but if you have less than that your battery life decreases exponentially...better to switch to 2g

liorry- looks like you've been whoring around and when you do that you need to cleanse your phone, I guarantee you have residual stuff left over from "other" roms that is causing your problems

the solution for anyone having problems is to

fastboot oem lock

then

fastboot oem unlock

this cleans everything.

then do a fresh install with NO restoring

If you want your angry birds high scores then have fun doing what you've been doing
[Nexus S Android Development] mortal300:
Please tell me what difference locking the bootloader and then unlocking does as opposed to

wiping partition

wiping cache

wiping dalvik

fixing persmissions

IMO it does nothing different. All it does it delete clockwork recovery and u gotta go through and install that again. I have never used any other ROM besides CM7. I rooted my nexus s and began with CM7. All the problems people are having are true and not because they are not wiping correctly.

Locking the bootload and unlocking serves no difference that wiping. Its like reformatting a hard drive. You just go into windows boot cd and format the partition and reinstall windows. You dont unplug the "bootloader" in windows and then plug it back in and then reinstall..simple concept. Wiping a phone is wiping a phone..

If you have proof of exactly the difference, i'd love to see ur factual evidence. I dont have proof for what i'm saying but i'm just following the boat that has been flowing for years with hardrive partitions...
[Nexus S Android Development] Sim-1:
How do you fix permissions?
[Nexus S Android Development] liorry:
Oh c'mon... I just said I used many other ROMs and all worked perfect for more than a week or two. I'm not flashing a new ROM everyday.

even if that's whoring around, why every ROM I used was great except CM?
[Nexus S Android Development] mortal300:
Go to clockwork and go to advanced then theres a fix permissions option

but it didnt help for **** for me. Still have issues up the ass
[Nexus S Android Development] ogdobber:
I don't have proof...just theories. So far everyone that has had "problems" and did the fastboot lock/unlock voila no more problems;)

soooo clockwork might not be doing the job properly :confused: just saying
[Nexus S Android Development] generalagony:
BINGO!!!! There was a post a while back that said that the dalvik wipe in CWM is not wiping properly. I use Root Explorer to wipe my dalvik in the cache and data directory before flashing anything and I have not had any problems since. When wiping dalvik in CWM I don't think it is going a full wipe and that is why there seem to be problems with it; so yes doing a fastboot oem lock/unlock clears everything and fixes most of the problems people are having.

on a side note. Does anyone know how I can get my swipe down gesture to open the damn notification bar like it used to before I updated to the stable build :P
[Nexus S Android Development] phillevy:
I have regretfully now moved away from CM7 due to repeated reboot loops (dimmed screen and black screen). I accept that wiping for a major release is a good idea, but in all the time i've been flashing roms (going back to my Hero 18 months ago) this drastic re-setting of everything including recovery and sd card has never been needed. I can't see why this should be neccessary with CM7 but not with all the other (more stable for me) ROMs available. Even Elelinux which is CM based only needed a wipe of cache/dalvik cache on the Hero with no instability resulting. Like others, I really like CM and what it offers, but for me this is not worth the hassle it is causing at the moment.
[Nexus S Android Development] ogdobber:
swipe down fixed in the latest nightly;)
[Nexus S Android Development] dont know:
In the FINAL version?

What's going on with CM? For the last years CM was THE ROM-devs. Now they have known major bugs (phone FC IS major for a mobile phone) in a final..?

In SupeAOSP the 2G/3G toggle works since 4 weeks...
[Nexus S Android Development] generalagony:
is everything else running smooth on the latest nightly? Don't want to fix swipe down and then be stuck with a buggy build :P
[Nexus S Android Development] Haizum74:
- Not frozen on me once.

- No sluggishness at all either, in fact its been rather nippy running at 1.3Ghz

- Mine lasted nearly 24hrs on one charge, plenty of usage too (on netarchy kernel)

- Maps does that on mine too although it did on other non Cyanogen ROMS

- Got an alarm clock for that lol
[Nexus S Android Development] mortal300:
How'd u overclock?
[Nexus S Android Development] oldblue910:
I'd still like to know why they either can't or won't fix the problem that CM7 has always had with the Google Voice app. If you open the app, then hit the back button, the app reopens, then pressing the back button a second time finally gets it to close out for good.

I know the CM team has a policy of not doing fixes for individual apps and instead leave that on the shoulders of the app developers, and rightfully so. However, in my opinion it's pretty clear this is a problem with CM7 and not a problem with the Google Voice app. It works just fine on the stock Gingerbread build on the Nexus S, and the new Gingerbread update for the Droid X. Just sayin'.
[Nexus S Android Development] mortal300:
Might not be? I've been doing the same thing with clockwork on 3 different phones for 2 years now with CyanogenMod. Tell me why in 2011 it suddenly it causing problems? =) c'mon man, were not all dumb here, there are issues and many fail to ignore it or pretend it didnt happen or blame something else.

Again. You did not read my post. I clearly said how I wiped EVERYTHING. PARTITION, CACHE, &&&& DALVIK CACHE, ANDDDDDDDDD fixed Permissions.

I did not JUST do dalvik. Dalvik doesnt even wipe the phone. Its for the JIT compiler and has nothing to do with wiping the phones memory of the OS. What do you think Root Explorer does? Some magical wiping technique? Clockwork does the same thing.

I will purposely do the fastbook lock and unlock today and reinstall CM. If it doesnt help...then i wasted my entire 1.5 hours trying to restore my apps and phone back to its normal state becus of that bs.
[Nexus S Android Development] Sim-1:
To do that, do you just select all the files within those 2 folders and delete them?
[Nexus S Android Development] ogdobber:
because in 2011 android/gingerbread started using EXT4.

In the past most (if not all) android phones used the YAFFS file-system...on the NS with gingerbread it switched to EXT4 which I believe the problem with clockwork lies..

yes then immediately reboot into recovey
[Nexus S Android Development] Sim-1:
I just did it, then reflashed the ROM but I still have problems with Gmail: text stops at half the lenght of the screen I messages don't sync automatically.

:o
[Nexus S Android Development] mortal300:
Ok i believe what your saying. But we'll see. I just locked and unlocked bootloader and did immediate fresh install of CM7 with Gapps after. No restoring no BS. (I never restore to begin with).

Let's see what happens....

**Any tips on where to overlock? I know its in CM settings but doesnt work unless u have appropriate kernel correct?
[Nexus S Android Development] mortal300:
+1 on the text stopping at half screen. Ur not the only one. Many others complained about that too.

So far sync has been ok for past 10 minutes...hah
[Nexus S Android Development] ogdobber:
right, that is a known problem with gmail...the only workaround is to rotate to landscape mode then back to portrait...it seems to stick for me after doing that once

look in netarchy's and morfics threads regarding overclocking...keep in mind that some phones don't like too much oc;)
[Nexus S Android Development] generalagony:
Correct.
[Nexus S Android Development] generalagony:
Chill out man. You are asking for help and so far I have seen at least three people try to help you. If you can't at least have the simple courtesy to say "thanks guys but that didn't work " go try a different rom and stop being an ass.
[Nexus S Android Development] ogdobber:
sometimes experience can be your worst enemy. "I have been doing it like this for years, why wouldn't it work now?"

well in 2011 things are different and the culprit is EXT4 or rather apps not being able to handle EXT4 properly

I can understand the frustration...but solution has been stated, and if you follow it, the only problems you will have is paginated gmail (workaround-rotate landscape and back to portrait) and a DO NOT PRESS ever! 2g/3g widget. ever!!

CM7 is absolutely fantastic.

when people are having problems and are unsatisfied it is disturbing...
[Nexus S Android Development] mortal300:
I'm not yelling...or "unchill" lol i'm trying to express that I'm not a super noob and kinda know what im doing. Mainly beacause i've tried everything ppl say already and there are clearly problems with the rom...idk why ppl ignore it. And i am thankful for the help. (like i said most of it is the same post over and over again..."wipe and reflash")

@ogdobber - thanks ill check out those kernels. Had a sync issue a little bit ago...we'll see what the other bugs do if they come back!
[Nexus S Android Development] matticala:
Just installed CM7 and it's just soooooo great! I'm loving it already!!!
[Nexus S Android Development] dont know:
vs

Sorry, a ROM (pretend to be final) FCing the phone app at 2G/3G toggle can't be fantastic. Per definition of "phone".
[Nexus S Android Development] NPS_CA:
Really puzzled by CM7 on newer NS's ; default CM7 kernel has MAJOR issues. CM7 with other kernels (netarchy) works perfectly fine. My symptoms are bootloops, hard kernel hangs (to the point the last_msg isn't available) and the standard dark screen/lit buttons (adb works but most of phone crashed). NO FC's though - so this is not a permissions issue.

I'm also suspecting Clockwork is not wiping things properly; so will try to oem lock and oem unlock and report back if default kernel works after that.
[Nexus S Android Development] dudeimgeorge:
lets be honest

amazing or not. this is not a final product still

I HAVE to press the issues again that dont work:

2g/3g toggle

lockscreen gesture crashes (cant do any contacts! what a must!!)

email real estate is a disaster and actually annoying to read (moving from portrait to landscape is not a solution...well it is..but..meh)

and other stuff i honestly forgot about.
[Nexus S Android Development] ogdobber:
can you 2g/3g toggle with a widget on the stock rom? is it so much trouble to open settings and click it in there??

lockscreen gestures, you can do all contacts just not an individual contact...I think that is pretty good (yes I am sure it will get fixed for an individual) but again...stock? no

email- I had it once and since the "workaround" it hasn't done it since...

Let me ask all you ungrateful f%!#s a question...how much did you pay for CM7??? What entitles you to this? The developers for CM7 don't get paid for this, sure people make donations...and thats because it is worth it!

What about all the awesome things that CM7 does??

if there are other roms that do what you need/want then go!! why are you trolling here?
[Nexus S Android Development] boostedfern:
I have this same exact problem.
[Nexus S Android Development] AndyCr15:
Take the picture and zoom in on that. Correct me if I'm wrong, but that's all a digital zoom really does...
[Nexus S Android Development] dskyers:
my phone wont root at all?
[Nexus S Android Development] SubyWill:
I also have that problem! I hope there's a fix because it's pretty annoying.
[Nexus S Android Development] crking1980:
He fixed it.. Should be in tonights nightly
[Nexus S Android Development] ryan562:
x3
[Nexus S Android Development] mortal300:
Did that..but don't think its the same. The picture wasn't clear however my friend who has a original moto Droid zoomed in and had to send me the pics

Do you understand how embarrassing that is!?! -_-
[Nexus S Android Development] yungfresh:
I'm curious..Is everyone jumping ship from the CM Nightlies and going over to the RC1? If so, why? just wondering if it makes sense to cross over now.
[Nexus S Android Development] chrlswltrs:
I did, just wanted to get on the rc to try some kernels, probably going back to nightlies next week
[Nexus S Android Development] aam6906:
its already fixed in build 42.......43 is tonights new one
[Nexus S Android Development] gratti:
I had that problem too, to fix out I simply rebooted my phone and the rotary wheel was gone. It didn't came back after the reboot either.
[Nexus S Android Development] stiefa00:
Anybody using adw luncher ex? I miss some paid features like annimations when scrolling my screens.

I wonder if there will be problems using EX instead of free ads.
[Nexus S Android Development] tcvaio:
่just flash theme tangerie theme and it changed the bootscreen too. Is there a way to remove the theme and get back the cyanogen bootscreen :(
[Nexus S Android Development] jonjon68:
Go get Boot Animations Installer from the market. It's a buck but works extremely well. Preview various boot screens, including CM, then apply and reboot.

I got it because while trying different ROMs is now history, I do still try a kernel from time to time and couldn't stand seeing a Team Whiskey animation on my phone. Morfic really should dis-associate himself from TW as the stuff he's done is actually pretty decent. Anyway, I digress.

This did the trick for me, but it should also fix you're problem if you can't back out of the theme. Either that or just reflash the CM zip file. that should do it as well.
[Nexus S Android Development] cyco1978:
Anyone notice that it never shows 3G. Jumps between H / E. When with other rom when I get in the phone it jump between 3G / H. Now it will just disconnect from data. Is there going to be a fix for that? Love rom no reboot!!
[Nexus S Android Development] tcvaio:
thank for your advice pal. Will wait for a next release ver and reflash
[Nexus S Android Development] stiefa00:
Tested and no problems so far
[Nexus S Android Development] jonjon68:
Reflashing current over the top wont, of shouldn't anyway, negatively impact your current phone build but should remove the theme. Fwiw

With that said, 43 is out
[Nexus S Android Development] sagarpruthi:
hi i just installed RC1 everything went perfect the phone rebooted with the Cyanogen OS as well but now its stuck on the initial animation of the android on the skateboard and its happening again and again for the past 10 mins. Please let me know what to do.
[Nexus S Android Development] zephiK:
No problems with ADW Launcher EX.
[Nexus S Android Development] mortal300:
Just for the record. I've done everything you have said from A to Z. My GMail and GTalk issues havent changed. My phone is locked and showing the reception bars green (of course meaning im synced with google servers). I unlock my phone then open GTalk and bam all the sudden they are grey and it says lost connection to server. I wait wait wait wait nothing happens. Gotta log out and re sign in. (Same problem as before ur instructions)

Not bashing...i just am trying to find a solution cus if all these ppl are saying htis ROM is amazing and have ZERO problems. I find it either hard to believe as in they are bullshitting and dont know **** OR i'm ****ing up on my end which i hope is the problem so thats why im here asking for help on what to do! But the help didnt help so now what do i do next?...
[Nexus S Android Development] ogdobber:
on wifi or 3g or both?
[Nexus S Android Development] Aria807:
My phone still gets similar issues. Sometimes when I unlock my phone, after a few seconds my reception and H/3G turns gray. But my stuff still work. I can still go on the browser and stuff loads or I can stream music off the internet radio as well just fine. It's just really annoying it never did it b4 when I was on #26.
[Nexus S Android Development] mortal300:
Both. mostly 3g cus I try not to be on wifi at school since im always walking around on campus and the signal drops when i get outta range of one router until i get in range of another.

So mostly 3g but def both. :confused:
[Nexus S Android Development] mortal300:
Yeah..weirddd issue cus **** still works lol
[Nexus S Android Development] YDardeer:
Chill man, no need to get all touchy about it. People wouldn't spend the time in this forums to post about their problems with CM if they didn't love this rom and wish all great things for the open source community . We are just stating our frustrations with this rom build in hope of finding a solution. We all still love cyanogencyanogen
[Nexus S Android Development] zephiK:
Some of you are posting your frustrations and some are completely bashing the phone by comparing CM7 on MT4G or whatever. Just my observations.
[Nexus S Android Development] sufibravo:
LOL...about time you lost your cool...anyway for those having bootloop issues..I'd recommend netarchy's kernel..even if you don't OC.
[Nexus S Android Development] KidCold:
Just woke up with bootloop issues. Could it be that it overheats? I normally dont use a case but i went somewhere that i needed one so put it on and left it on overnight.
[Nexus S Android Development] phillevy:
For me CM7 + Netarchy gave frequent dim screen bootloops. Netarchy is fine though with infin1ty so I think it is definately CM problem, not kernel.
[Nexus S Android Development] tommyz2kool:
Does this happen on stock rom too? It's been a while since I've been on stock and the gray bars thing is annoying.
[Nexus S Android Development] adityaw:
I'd second this. No more reboot problem for me after netarchy.
[Nexus S Android Development] steve.garon:
+1 Netarchy's kernel has been great for me. 1.3 GHZ overclock is rock solid. (1.4 reboots but I guess my phone doesnt like it)

Also I suggest BFS. It fell a lot faster to me than CFS especially in the web browser...

Steve
[Nexus S Android Development] dsellers2:
+1 with og's cool. Never seen it before but I like it. Haha. :)
[Nexus S Android Development] brian6685:
I'm suprised he didn't lose his cool earlier... it's ridiculous how ungrateful people can be considering how much work is put into the cm project as a whole. If you don't like it use something else. There is a difference between having a problem and trying to resolve it and bashing cm in general because it's not final "in your opinion." Take a look at how many devices they have support for and how many devices are now able to use gingerbread because of cm that probably wouldn't ever be able to. Sorry for the rant but I needed to express myself.

Nexus S
[Nexus S Android Development] burnfire:
Love cm.. And all other roms
[Nexus S Android Development] Vandam500:
After a couple days without waking up to a infinite boot loop, today I woke up to find it looping again :(. Thank goodness I woke up by myself cause if not obviously the alarm wasn't going to sound off :/
[Nexus S Android Development] Darrien13:
Is anyone's else battery life terrible running final
[Nexus S Android Development] Aria807:
It very rarely does it on stock rom or when I was on RC1 and RC2 and #26. This was a new issue introduced since I flashed RC3, RC4, and 7.0.0. The only time it ever does it on those RC1, RC2 etc was if I got into an elevator and it completely loses signal. Now it just does it almost every time I unlock my phone. It's really annoying. Does anyone else have that issue?
[Nexus S Android Development] dsixda:
Guys and gals, let's keep the flames and obscene comments to a minimum. Bad language is against the forum rules and will not be tolerated - keep in mind the audience visiting this thread, both young and old. Bickering and swearing amongst each other is not going to resolve anything; I advise you file a bug report (if it hasn't been filed already) if you notice a problem.
[Nexus S Android Development] gasparzim:
When I try to watch youtube, I get just a green video. Anyone else having this?

I´m on latest CM7 with netarchy 1.3.0.

EDIT: NVM, fixed disabling Image Quality under Performance menu (CM Conf)
[Nexus S Android Development] KidCold:
Just tried it now. Works fine for me
[Nexus S Android Development] Bolick:
Got CM7 release with "stock" kernel (I mean kernel from CM7) flashed after OEM Lock-Unlock, formatting data/system/cache partitions from CWM.

After about 30 hours uptime got black screen with buttons lit.

Device was just lying on the table, no charging, no 2g/3g toggling, nothing.

The same I saw with RC2 and RC4.

I removed battery and booted into normal system.

Unfortunately I didn't found /proc/last_kmsg and anything in /data/dontpanic/.

So I don't know if it is possible to get any data about circumstances caused this hanging (

Quite disappointed of this behavior.

Stock ROM was running for a week last time without any noticeable problem, but I was missing those little enhancements from CM7 so much that decided to give a try with CM7 release. So sorry to get problems here.
[Nexus S Android Development] tvhoesel:
No extreme battery draining here with CM7 final.

If Maps is draining your battery startup Latitude and disable Automatic Check-in.

After that exit Latitude through the last menu-option Sign Out Latitude.

This helped for me saving 25% battery.