yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] jtn7040:
happened to me once.. don't just reboot shut down the phone completely leave it off for a bit and restart... worked fine for me after doing the above
[Nexus S Android Development] peeturr:
Capture video for MMS working for anyone? Not sure if this had been mentioned before but it hasn't worked for me on any nightlies either.
[Nexus S Android Development] jonjon68:
Wipe cache and factory reset, wipe Dalvik cache and fix permissions, reflash ROM then gapps. Reboot at least once if you're trying a not CM native kernel.

That should fix pretty much anything as long as there isn't something wrong with the zip file you're using and/or the contents within.
[Nexus S Android Development] fabio008:
Thanks! I'm gonna try that again soon (had to go back to stock ROM for a while). I tried following all the "cleaning" steps from this reference post: http://xdaforums.com/showthread.php?t=955719

but looks like I missed something (I didn't fix permissions initially, could be that).

One other thing I noticed, I tried registering for updates in the CM7 Settings but there was no reply, no matter how many times I clicked the "Register" button
[Nexus S Android Development] jonjon68:
I tried that today for the first time as well. Same result. I still get random notifications in RM that new builds are available. I always assumed it was a default thing. End of the day not being registered doesn't matter to me. Besides getting notifications I have got in to a routine of checking manually, either on the teamdouche crespo build mirror, or via Rom Manager. I guess the auto notify might save me 20 seconds a day or whatever. <Shrugs>
[Nexus S Android Development] simms22:
you could always check my tweets too, MUCH faster than rom manager :rolleyes:
[Nexus S Android Development] solarus2011:
Anyone else having issues with apps that require root permission. Titanium Backup and Root Explorer will sit at "Requesting root access" or black screen respectively. Same has happened with ROM Manager and QuickSSHd. The only way to get them work is to "clear data" in Applications settings.

Also a reboot to recovery and "Fix Permissions" seems to fix the issue also.
[Nexus S Android Development] simms22:
im assuming that you are using a kernel with bfs. if its a trinity kernel, the newer kernels do not include bfs. if it netarchys kernel, he has cfs versions. i suggest those.
[Nexus S Android Development] IcOpRo:
Has anyone been able to use the CPU Freq Settings on CM#7??? I cant get it going it just FC's on me.

It works on my Wife's MyTouch 4g. But no matter how much I try to enable it in my NS it dont work. Maybe it just doesnt work on the NS.

We was just curious.
[Nexus S Android Development] simms22:
it doesnt work for the NS yet.
[Nexus S Android Development] IcOpRo:
Thanks a lot, thats what I figured... Cant wait to have that working on the NS
[Nexus S Android Development] lilnev:
Crash/Freeze - Half Dimmed Cyanogen7 Boot screen

With CM7 I'm experiencing that my phone crashes on a regular basis. It hasnt crashed while actively using it, it's always happened either over night or in my pocket.

When it crashes, the screen shows a very lightly lit up CM7 boot screen and all 4 bottom buttons are lit fully.

I came from stock ROM with a clean wipe, but this happened to me as well during the early nightlies.

The only way to fix it to take out the battery and reboot.

Has anyone else experienced this?

What logs can I provide when this happens?
[Nexus S Android Development] irishrally:
I've experienced this too. It may be the Google acknowledged reboot bug; I don't know.
[Nexus S Android Development] solarus2011:
I was using the latest stock + voodoo from Trinity. Switched to one of the cfs OC and seems to work great now. Thanks for the assist.
[Nexus S Android Development] simms22:
this version of cm7 is ancient in terms of custom roms. instead of flashing 7.0.3, you should be flashing a nightly(until 7.1 hits). there is no point complaining about bugs in this ancient version of cm7 :p
[Nexus S Android Development] sloppy1:
how far away is 7.1
[Nexus S Android Development] sinik420:
Read a few posts up, some are saying this weekend if all goes well

Sent from my nexus on a kang from simms
[Nexus S Android Development] IRIE4IPIER:
no, this guy was probably overclocking to 1300-1400, thats when you get freezes and reboots. I put it down to 1200 and i have not had a reboot, or any other problems since, i also uninstalled setcpu and just use the built in cpu manager in cm settings. back when i was using setcpu and overclocked to 1300-1400, this phone was a reboot machine.
[Nexus S Android Development] Vandam500:
All the nightlys have given the same experience.

Sent from my Nexus S
[Nexus S Android Development] Haizum74:
Mine keeps 'booting' to the sim password screen every so often.
[Nexus S Android Development] robto:
Totally agree. Seems to be something in current CM framework Nexus s does not like. CM was super stable in Desire but ….. not in Nexus s. I recently flashed Oxigen, “similar” to Cyanogen, and my nexus seems to be stable now. So I think I will keep Oxigen for a while.

BUT, I have to say I like Cyanogen and I do appreciate their great effort and dedication. It is really fantastic to have the option to use Cyanogen. I am sure I will go back to Cyanogen one day. So I would recommend doing a donation anyway.
[Nexus S Android Development] gu1dry:
CyanogenMod 7.1.0-RC1 is now available, link.
[Nexus S Android Development] racker:
I tried 7.1.0-RC1 after having the same bootloop problems with 7.0.3 stable. same result - bootloop while in standby.

FYI
[Nexus S Android Development] simms22:
try a cm7 nightly, the cm7 stable hasnt been updated in a while, and its not so stable. the nightlys(or kangs) have been updated, and have the latest bug fixes. ther are much more stable.
[Nexus S Android Development] woosie:
Where nightlies?

Where can we get recent nightlies ? Team douche mirrors stopped update after #180, since 31st Aug.
[Nexus S Android Development] matt2053:
That is the latest nightly. But it is far newer than 7.0.3 stable, which was build at the beginning of May.
[Nexus S Android Development] RcrdBrt:
They have started compiling again

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] Shivammcool:
Yep... This is nightly 199
[Nexus S Android Development] eridroid:
you themed by urself? is this nightly stable enough?
[Nexus S Android Development] EraqEE:
I installed this rom today and I was looking forward to the feature which allows you to revoke permissions from certain apps.

Problem is, I don't see this feature on my phone. I checked the Cyanogenmod Wiki and it says that it should be located under:

Cyanogen settings ➔ Applications

I did just that and it's not there at all so did you guys remove it from this version or something?

Edit: Never Mind, this option is only available in the 7.1 Release Candidate version
[Nexus S Android Development] lilnev:
It's not a reboot, it's an actual _crash_. This means the alarm doesn't work in the morning and I have to use my wifes iPhone alarm. How embarrassing?
[Nexus S Android Development] cuban88:
(no service)

Anyone else experiencing issues with loss of service? I am going in and out of H and X.

Any fixes? Only happened since flashing CM7 rc1
[Nexus S Android Development] suhas_sm:
Two things.

1. Resolution of my doodle jump changed :( As if resolution has doubled .. the doodle looks much smaller :(

2. Unable to register with the update servers :)
[Nexus S Android Development] tcvaio:
This rom is working great. And it does comsumer battery so much and run out so fast though.:o
[Nexus S Android Development] gratti:
Today I couldn't get a gps fix for the life of me, I tried everything, using gps position app to reset the internal gps state, tried rebooting, reflashing cm7. It use to work just fine with stock rom, witch I'm going back to until cm7 becomes stable.
[Nexus S Android Development] liquelt:
Do I have to perform a Full wipe?

I am running CM7 Nightlies Build #2.

What is the big difference between the currently nigthly build?

Thanks.
[Nexus S Android Development] docsamsom:
Is the free navigation software not included in the rom?
[Nexus S Android Development] 651stp:
still having random vibrates here and there, same with nightly's. Vibrates sometimes when the screen is off and when im pressing on the screen without long clicks.
[Nexus S Android Development] 651stp:
no u dont need to wipe, i usually just wipe cache and delvik cache in advance settings in recovery then flash. cheers.
[Nexus S Android Development] 651stp:
download maps from the market then it should install it.
[Nexus S Android Development] simms22:
i found a HUGE bug in cyanogenmod7 effecting all phone models. this might make ppl rethink using CM7. the info is posted here http://goo.gl/AZDtZ
[Nexus S Android Development] docsamsom:
Thanks. However, car mode does not work as well. It gives me the notification that it's in car mode when it isn't.
[Nexus S Android Development] hkt03:
As much as I want to flash this on my new Nexus S.. think I'll wait till the stable release comes out.
[Nexus S Android Development] simms22:
thats your decision to make, but its as stable as stock and more functional ;)
[Nexus S Android Development] chrlswltrs:
Completely agree, plus add in a different overclock kernel and this phone flies!
[Nexus S Android Development] sonnysekhon:
Thanks, that made my horrible day a little better :).
[Nexus S Android Development] glasslung:
I can't seem to access the service mode menu using *#*#197328640#*#*

Nothing happens when I type it in. Is there a fix for this?
[Nexus S Android Development] jonjon68:
Can't agree with that personally. My phone is becoming more unstable as the builds fly out. As a huge CM fan I've getting really nervous about it frankly. I couldn't have imagined myself going back to stock from a CM build before this but I'm pretty close to it. I've rebooted and and/or crashed 5 or 6 times today. By far the most I've bounced like this. Few other anamalies as well.

Not my intent to discourage exploration with CM ROM Mods but I will say it's definitely not unanimous that RC1, or any other CM7 NS build is stable as stock and more functional. For me at least, it's less on both counts and regressing, not progressing.
[Nexus S Android Development] yungfresh:
I agree with you on this. I find that everyone seems to have their own version of "stable". I find it best to flash whichever version gives you what you need to use your phone for and find the right kernel and just sit tight for them to come out with a stable build. Hopefully that happens soon. :D
[Nexus S Android Development] slowz3r:
A hole *angry bird face*

lol
[Nexus S Android Development] robstunner:
Hows battery life on this? When I went to #42 build, i found my battery life got cut in half. Since #42 and RC1 came out at the same time i didnt bother, but can anyone help me out?
[Nexus S Android Development] sagarpruthi:
Everytime i try to access CPU settings in CyanogenMod Settings -> Performance -> CPU Settings, it crashes and gives me this error - The application CyanogenMod Settings (process com.cyanogenmod.cmparts) has stopped unexpectedly. Please try again. Please help what to do. And after installing CM7 my quadrant score from 1800+ has reduced to 1500+. any help on this topic would be appreciated.
[Nexus S Android Development] jonjon68:
That would be the intellectual approach. :)

Although I am not in to the unusual and fairly inappropriate adoration (professing love etc..is just a bit disturbing to me) that some give the kernel and ROM mod builders on here, I still do have a slight illness to trying new builds. Yesterday's experience on my phone may just cure me of it if ongoing builds don't tighten up. But yeah, sitting on a stable ROM and kernel is the way to go if you can manage it.
[Nexus S Android Development] mojonation1487:
I would say its your phone instead of the cm software. The majority of us have no extra problems than the stock software. Personally I have ZERO problems with anything unless I put an overclocked kernel in the mix.
[Nexus S Android Development] big_adventure:
Two or three extra cents:

I got pretty poor battery life (about equivalent to my old N1) from me NS using nightlies from about 10 to 37 on work days - my office gets terrible signal and it flips often between Edge and HSPA, as well as synced and unsynced. I also veeeerrrrry occasionally got the "faint" CM boot screen hangup when it was in my pocket - only a battery pull would fix that, but it only happened aboout 5 times.

Nightly 39 and than the RC1 seem to have fixed every problem for me. Network signal is still poor, but seems MUCH more stable at work - it stays synced and stays on 2-3 bars of "H". Speedtests show lousy downloads, but that's a known problem on the 3G tower I connect to here, and one that always seems much worse with Infineon chipsets (iPhones and others using infineon chips, which I believe the NS does, get even worse performance on this tower than other chipsets).

Most impressively, battery life has doubled - with moderate use, before N39 I'd be around 25% or less by 7PM (after unplugging the phone at 7AM or so). 39 improved on this and the RC is leaving me with more than 60%. I'll need some more testing to confirm everything, but so far it seems really good. Obviously, not everyone is having the same experience, but I have definitely noticed a massive improvement.
[Nexus S Android Development] simms22:
it doesnt work for the nexus s yet. use setcpu or something similar.
[Nexus S Android Development] jonjon68:
Sounds logical with the information you have however runs wonderfully stable on Stock and Modaco. And started out pretty strong on the early CM builds.

I get your phone is fine and so on and so forth. Doesn't mean my phone is defective. If it were, it would have likely manifested well before this. I was fine with the marginally unstable nature of the crackflash builds and on in to the early published CM uploads. But it's gone progressively downhill.

So far today I've completely wiped including cache, dalvik, permissions and haven't had an issue. Not holding my breath though given my recent history.

I'm going to hang in there for now but it's not my phone.
[Nexus S Android Development] kenvan19:
Between 14 and 16 hours clocked at 1400/100 of moderately heavy to heavy use.

Sent from my MattedBlues CM7 Google Nexus S!
[Nexus S Android Development] hungyip84:
I found a bug today.

I tried to play with the notification bar toggle a little bit today by enabling/disabling some of the toggles. Then suddenly the "Toggle 2G/3G" item is disabled. And when I navigate to mobile network settings, the "Use only 2G networks" option disappeared.

I rebooted my phone and then went into endless "com.android.phone" force close problem.
[Nexus S Android Development] docsamsom:
Am I the only one not able to get car home mode? If this isn't a common issue, might rewipe and install again.
[Nexus S Android Development] mojonation1487:
Did you have a different kernel?
[Nexus S Android Development] jonjon68:
I've played around with most available. Even team whiskey, where I expect flaky. And not dissapointed there but point is, I have tried all of them on XDA for the NS.

Right now, after fully wiping once again and installing #3 from scratch and using Netarchy's CFS kernel, seems to be pretty stable.
[Nexus S Android Development] robstunner:
Did it get better after a few days? Or was it the same all around?
[Nexus S Android Development] jonjon68:
Better? 14+ hours on a single charge? Never happened for me. All about usage I suppose but getting a full day of use on my android smartphones has been pure fantasy. 14-16 hours. Just got a lil chub thinking about it. :D I'd have to more than double my typical time period before plugging in. More than 5 or 6 hours, for me, means I'm not on my phone very much at all that day, which means it doesn't happen. Damn evil phones. :)
[Nexus S Android Development] robstunner:
really? I'm on CM7 RC1 now but i was consistently hitting 18hrs daily when on the stock rom.
[Nexus S Android Development] docsamsom:
Crash with endless loop of booting up

Had my first random reboot after installing the rom almost 36 hours ago. Went to bed last night with 72% battery remaining....left the phone uncharged to see how much drained overnight. Woke up with 62% remaining...which I thought wasn't bad.

Within half an hour, found the phone doing an endless loop of a partial bootscreen animation ( just the bottom half of the X...i have got a theme installed which is why I dont get the Cyanogenmod bootscreen). Had to remove the battery to reboot. On rebooting, the battery had already dropped to 42%! Thats a 20% drop in half an hour with the phone in sleep mode.

Random reboots are something you can live with...but if it crashes and gets stuck in an endless reboot mode, it becomes too unreliable in terms of alarm, expected calls, etc.....

Might get rid of the theme to see if thats the problem.
[Nexus S Android Development] AndyCr15:
Wow, I think I could use it for 5 hours straight and it would only just fail. What on earth have you done to yours?!?!? (And yes, it is what have YOU done, this phone can go 30 hours, change some settings and apps and it will go 10...)
[Nexus S Android Development] gaijing:
I got exactly the same behavior on mine...
[Nexus S Android Development] wargy:
The exact same thing happened to me yesterday while on the train (I was trying to save some battery by switching to 2G networks) and after a reboot, endless "com.android.phone" FC's!
[Nexus S Android Development] jonjon68:
Yes, I've put a voodoo spell on it to kill my battery performance. sigh.

I may have to test continuous use one day and see what happens but generally I'm not too far off that anyway many days.

Nope, sorry bud. I'm happy for you and your usage. That's what allows you to have long battery life. That's what I did and do to my phone. And what you do to your phone to allow a day of use, is not use it like I do. That's what you do to your phone. Probably should stick to giving out opinions to your phone. You know exactly jack about mine, what I do with it, and how I use it.

With that said, and you properly put in your place, I do what most everyone in these forums do. Try different builds, different kernels and so on. I condition like most. What I do differently apparently, is use it excessively.

But that won't change, so I'm stuck with what I have. A 1500 or 1600 NiMh battery (whatever it is) that does what it's capable of. While you do what you do with your battery and what it's capable of.

But thank you for attempting to know what I do. Failing miserably and coming off as a tool. But A for effort.
[Nexus S Android Development] solarus2011:
Its a known issue that has been discussed. Use the search function for "car home" and you should find a link to a working copy. Install it after flashing CM and gaaps. I use Root Manager.
[Nexus S Android Development] mortal300:
Where are the nightlies for this rom?
[Nexus S Android Development] AndyCr15:
Ha ha, you're funny.

Where have I said I know what you do? Read again and in fact I'm asking what do you do with yours and I'm saying it's all about how you set it up. I've not even said you've done anything wrong...

Sorry, not put in my place by your rather feeble attempt. Have another go perhaps?

Do it quick though, your phone might die during your reply...
[Nexus S Android Development] alanine:
I have the same reboot+endless loop problem, and I use the default theme. It has happened 3 times in the last 2 days.
[Nexus S Android Development] sweetpiggy:
me too had the 'phone crash' bug...... :(

solved with a factory reset from recovery :)
[Nexus S Android Development] Michigan Jason:
Battery life

I apologize if I am bringing up a dead discussion, but has anyone found a kernel for this rom that will give the best battery life. Running the nightlies I was able to get 36 hours with bluetooth on and pandora streaming for at least 2 hours a day. Now I get 13 hours without using set cpu. Any kernels that work well with this rom?
[Nexus S Android Development] sweetpiggy:
happened again:

I turned off the nexus to change the sim and when I rebooted that mistake again.

resolved by restoring a previous backup
[Nexus S Android Development] AndyCr15:
I've had the 'dim screen bootloop' 4 times this afternoon at the gym. I didn't have it at all in the first few days. :( I've just done a cache wipe, dalvic wipe and fix permissions to see if that helps...
[Nexus S Android Development] simms22:
if im lucky, if, i get about 8 hours. if most these users are heavy users, then im an exyremely heavy user. this morning i used 40% in 2 hours. but, seeing how i use my phone, im happy with that :)
[Nexus S Android Development] jonjon68:
I wouldn't say I'm happy but I'm not angry about it. It is what it is.

I think we are probably pretty similar in usage. I may have used some hyperbole butnot much.

Took my phone of the charger at 6:30 this morning. It shut down at 12:30. I was on it most of the morning however. Played rocket bunnies for 30 or 40 minutes. Angry bird seasons for another 30. Showed a few videos I had been working on. Watched a few YouTube videos and so on. Uber heavy use and that is typical. 6 to 7 hours is probably more accurate than the 5 to 6 I claimed in my previous post.

Conditioning isn't useless but until they take these phone to lithium ion or whatever the damn iPhones have since they dominate every smartphone battery table I've seen, then I'm stuck with what I have. Since going to an apple product isn't an option I can see taking.
[Nexus S Android Development] radlink14:
Bit of a side question but... if unlocking bootloader voids your warranty, can you re-lock it in case you have to take it back?

I have insurance through best buy, you guys didn't get it?
[Nexus S Android Development] mcosmi:
goggle hard reset, anyone else?

Google goggles hard resets phone...wierd...cm7 with matted blues, and netarchy cfs.
[Nexus S Android Development] footballpics.info:
1st: thx for the RC1 - its really cool and works fine

2nd: can someone say something about when 2.3.3 comes up?

greetings flo
[Nexus S Android Development] simms22:
yes. the same way you unlocked it.
[Nexus S Android Development] :
yea i'm the same way. if i get 8 hours of solid usage i'm pretty happy.
[Nexus S Android Development] saryu:
hi.. been using this ROM for 1 day and i encountered some nasty bug. It's not happen everytime but if i left this phone with screen off for quite some time, when i get back to my phone, no matter what i do i cannot turn on the screen. I thought my battery died but i just fully charged it about 3 hours before, i tried to took out the battery and it works again. Running on RC 1 CM7 with lucid theme for RC 1. I didn't change the kernel before, already tried clear cache and dalvik and reinstall the RC1..
[Nexus S Android Development] simms22:
most likely its the theme.
[Nexus S Android Development] drew_grant:
I haven't had any of the issues you all are having (thank God) but I've had a pain in the ass issue with wifi and bluetooth last night with none of them wanting to turn on and when I did get wifi on, it would stay stuck on. I get the dim boot screen only when I play music and it's rare. One thing I got pissed off with, and this literally just happened, all my text messages just mysteriously disappeared. Other than that, I'm waiting for RC2.
[Nexus S Android Development] suhas_sm:
My lock animation had stopped working :( I reflashed it. worked for sometime again stopped :( What could be the reason ? is it a bug from cm7 ? :(
[Vibrant Q&A, Help & Troubleshooting] regP:
For some strange reason when I connect to PC for mass storage the external sd card shows up as a CD drive instead of a removable drive. The interesting thing is this only happens when I have voodoo enabled. If I disable voodoo everything mounts perfectly. I've tried flashing the mount fix in clockwork with no luck. Was on Axura 2.2.6 when I noticed the issue. Thought flashing to Axura 2.3 would maybe fit it but its a no go.

Anyone else experience this?