yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] jonjon68:
I enjoy my phone. I do wish it were by a different Mfg but I wanted CM and my vibrant and Galaxy S were obviously not going to get it natively. I also do hope it's not CM that makes the NS even worse that it is with the stock OS. Not so much I'll go back to stock, or any other mod for that matter. It's still better than an Iphone, BB, or Android AOSP phone.

It is what it is. We deal with the instability of this phone and carry on.

Yes, and your post are so much more useful. ;)

Opinions again which is what is supposed to make the forum fun for those that participate. In my 15 years on message boards and historically tech boards, xda does seem to have the most populous contingent that can't accept opinions of others without attempting to diminish their validity. I accept you've had a great experience with your phone. End of the day, you're unwillingness to accept your experience isn't shared unanimously isn't relevant to my participation on here. I've gotten used to the greasy kid stuff. Until there's a better BBS for smartphones, specifically Android smartphones, I'm stickin around here. At the moment XDA, warts and all, is still the best resource for information and software modifications.
[Nexus S Android Development] zephiK:
I know what you mean by that. I've debated about some of the most 'stupidest' things on XDA. As obvious as it was, somebody had to play devils advocate and just try to defend themselves no matter what.

I'm just saying that, without the bugs then Android wouldn't be as fun! It's just something we have to deal with. We can all admit that we are addicts at flashing ROMs because I sure am. But I still believe the annoying bugs that makes your phone fully dysfunctional can be fixed by simply wiping factory/cache/dalvik and starting everything from scratch. But people are always so scared and anxious to experiment things before doing it. If its such a problem just make a nandroid and play around with the phone. It's really difficult to brick this phone, just don't do anything absurd (this isnt directed towards you but in general).
[Nexus S Android Development] ykphuah:
FWIW, this happens to me on stock as well.
[Nexus S Android Development] Aria807:
Anyone else having reception bars graying out issues?
[Nexus S Android Development] fixedonfixies:
I kept falling for this nasty bug whereby i loose my Network Connection, "No Service" at random. Ive had to deal with it by a factory reset but I can be doing this everyday, but today i ran into this forum thanks to someone on here,

http://code.google.com/p/cyanogenmo...=ID Type Status Priority Device Owner Summary

and am going to give it another try and stay away from the steps to reproduce the problem.

Hope its of help to someone in the same predicament
[Nexus S Android Development] gasparzim:
Hmm, nope, ADW EX... tried to reproduce that bug again, but widgets loaded ok.
[Nexus S Android Development] fixedonfixies:
I do have this second bug which am not so sure is a general bug. But has anyone flashed the bfs Netarchy 1.3.0.x on CM7 RC4? I did and every time I do I loose my Boot Animation.

am duplicating this post under Netarchy's thread and will update both with any useful advice for other users to find.
[Nexus S Android Development] zephiK:
Yes the BFS removes boot screen but it does boot. It's in the FAQ of the Netarchy kernel thread.

To workaround this.. use the CFS version and it's fine.

Regardless of any ROM you use. As long as you use the BFS version, it wont display the boot animation. But it does load.
[Nexus S Android Development] DLFB:
I was using Nightly 26 for a week or two (w/ KB3 + Netarchy 1.3.X) and it started crapping out lately (RANDOM REBOOTS GALORE!). I dont get it since it started out quite well but lately it's been giving me a headache.

I just went with the RC4 now and hopefully it's stable. This is the final straw and if this craps out over and over again I just gotta find another ROM.
[Nexus S Android Development] hansmrtn:
Aww, who doesnt love CyanogenMod. I dont think I have had even one major problem.
[Nexus S Android Development] :
Agreed, the only problems I really had was with youtube playing videos, and the occasional reboot. But that's basically gone now, I usually go for weeks without anything wrong.

-I wrangled together some consonants and vowels and created this post-
[Nexus S Android Development] kemsiro:
deleted.

===========================
[Nexus S Android Development] Typhoe:
Black screen of death...

Hi,

I'm using the RC4 and have got a problem with it.

The phone "dies" with the soft bottom buttons backlighted on but nothing displayed on the screen (it seems off).

No button action seems to works (back/home/power...).

The phone is hot (not too much, but as after a long phone call).

All I can do is remove the battery and the phone boot ok and seems fine after that, till I have this problem again (I've got it a few times now).

No particular action seems to trigger the problem.

Here're the logs I get:

last_kmsg

pastebin.com/9efmLcjn

logcat

pastebin.com/HSQ7ZL7k

(sorry, no direct link, due to board policy to new users)

Is there anything else I can provide to help debug this problem?

Thank you,

Typhoe
[Nexus S Android Development] jonjon68:
I would post in the Cyanogenmod forum for the NS if you want to help them debug an issue. If however you just want your phone to function, I'd do a full wipe. Data, Cache, and then I usually wipe dalvik and fix permissions before I boot in to the MOD for the first time.

Wiping can fix some ills, especially if you came from another ROM without doing so. Even if you are coming form a previous version of CM7, it never hurts other than dealing with apps and it's data, but there are methods for easing that pain.
[Nexus S Android Development] Typhoe:
Hi,

I'll consider posting on Cyanogen Forum too...

I must concede that I didn't think to post there (remembering only to to NOT ASK/POST about nightlies) but indeed, as this is a RC...

On the other suggestions you make, I already did a full wipe (before install of the RC) and tried the cache/dalvik format... to no successful extend...

Thank you for your answer anyway!
[Nexus S Android Development] B52:
Awesome!!...haven't found any bugs yet

but the battery life like suck, and drain very fast. (down from 60% to 29% in sleep mode).
[Nexus S Android Development] bossarts:
It really works like a charm. Battery live is good as well. No bugs so far. I just have one problem with my preferred app:

Laut.fm (music streaming app) Version 0.44 (latest)

If i try to open it i get a FC, the problem is the process:

de.taukon.laut

Uninstal, cache cleaning ect. did not help. It works perfect with stock ROM.

Regards,

Nboss
[Nexus S Android Development] stiefa00:
I missed the last nightlies (and so the netarchy oc kernel). Netarchy kernel is nice for RC1, too?
[Nexus S Android Development] mrmarshall428:
Irishrally what are your settings for Watchdog? I have it and nothing seems to be out of control and my battery life still sucks! And what should I be looking for??
[Nexus S Android Development] smelian:
thank you for great rom

i have problem im getting : The process com.android.phone has stopped unexpectedly. Please try again.

when i go to SETTINGS - WIRELESS CONTROLS - MOBILE NETWORKS i cant find NETWORK OPERATORS so i can chose my network Manuel

and the air-plan mode check and unchecked alone
[Nexus S Android Development] jollerbarn:
Wow.

My first time on Cyanogen having run just about every other mod on the forum. I'm deeply impressed. The level of polish and speed is just in a different league. Great work! Thank you for your time.
[Nexus S Android Development] insanemachine:
Can I do app backup with titanium on stock with morfic's kernel, install CM7, and restore all the apps? Obviously not the system apps.

Sent from the bushes beneath your window
[Nexus S Android Development] thomasck:
#41 = RC?!
[Nexus S Android Development] zephiK:
Yes. Backing up applications doesn't matter what kernel you're using. It'll work
[Nexus S Android Development] tcvaio:
Wooooow , what a rom !!!!!!!

Luv it :D
[Nexus S Android Development] smelian:
any way to solve my problem i really like the rom but cant use it with FC all the time and cant detect my sim card , cant file network operator
[Nexus S Android Development] simms22:
restore your last backup(in recovery) then reflash the rom and gapps.
[Nexus S Android Development] AndyCr15:
So a couple of days back I thought I would try MoDaCo's ROM, as I heard it had better battery life. I wiped, started fresh and sure enough I was averaging 4% ph on a normal day, out and about.

Then along comes the RC1 and I'm tempted back again (mainly as I missed the notification bar toggles) so I wiped and started fresh again. Today I averaged 3.7% ph. Off charge at 6:30am, home at 6pm and still on 58%! That's far better than I got from any nightly's.
[Nexus S Android Development] brian6685:
I dunno how you get that good of battery life with stock kernel on rc1, I don't. I wish i could...
[Nexus S Android Development] jlevy73:
Depends on so many factors. It's almost impossible to compare two different users. If I can make it 8 hours on a single charge It's a good day for me.
[Nexus S Android Development] brian6685:
Yeah i feel ya lol
[Nexus S Android Development] baolongn:
Same here.. I got almost 200 MB running services. I don't know why.
[Nexus S Android Development] gratti:
Just flashed the RC1 and i found a bug.

AirSync from DoubleTwist stopped working. I can pair ir with the mac application, but it doesn't sync at all. After the inicial pairing, the device connect and immediately disconnect. And he keep doing that, connecting and disconnecting.

Use to work fine with stock, but now it's broken. I tried reinstalling and reflashing the room, but no luck there.

Aside that, is a great room, as usual.
[Nexus S Android Development] mortal300:
GREAT rom, but why the hell can't i still zoom in my camera app!!! This is such a crucial feature for everyday use.

I want to copy notes off the board but I can't zoom in to take a picture...:confused:
[Nexus S Android Development] glasslung:
The background of the call view (the screen you see when you're in a call) has the same rotary dial that appears in the lockscreen. The rotary dial doesn't appear to be functional; it's hidden behind the 2 rows of buttons (speaker phone, bluetooth, etc). Is there anyway to remove this background?
[Nexus S Android Development] tadaha:
I got the same problem too. Once on rc4, and another one just a couple of hours ago after I flashed #35
[Nexus S Android Development] damngood98:
i've seen this twice on my phone. i've only had the ns for about a week. do you guys use no led? i just assumed it was something with that. after uninstalling it i haven't seen it back yet.
[Nexus S Android Development] Typhoe:
Yes, I use it too.

But I've got this problem at least one time before installing it (that I'm sure of).

For how long haven't you see the problem (and have removed noled) if I may ask?
[Nexus S Android Development] Aria807:
Lol I've been putting up w/ that phone locking up and being really warm for the past few months. Ever since I installed RC1 thru every single RC. Happened few nights ago too on RC4.
[Nexus S Android Development] BrokenWall:
I have had my phone running for 92 hours with alot of usage. I found the fix to the reboots for me was to take it out of my S Shape TPU Case that alot of people love. After doing so the phone no longer reboots on me. I wonder if it was a heat issue. It use to reboot at stock speeds too so.

Now 100/1300 with no problems
[Nexus S Android Development] Bajo76:
I experienced a perfomance boost while browsing if i disable "Dithering" in CyanogenMod-Menue.

Even heavy sites like pocketnow.com (desktop version) are really smooth now.
[Nexus S Android Development] fabio008:
Wi-Fi Tethering

Just noticed this today, every time I try to use the Wi-Fi Tethering it always seems buggy. The connection is painfully slow and I rarely am able to properly connect to a website in my laptop.

I noticed this happening since RC2, is anyone experiencing it too?
[Nexus S Android Development] :
I haven't experienced that issue, why not just use usb tethering if you're using it on your laptop? I used it on my desktop and it runs beautifully.

-I wrangled together some consonants and vowels and created this post-
[Nexus S Android Development] fabio008:
USB tethering actually works the same way :(

It's not smooth at all like what I had with stock before. I'm just using og's Jame Bond kernel, no overclock, nothing.
[Nexus S Android Development] :
It may be the kernel itself. I am using netarchy's latest kernel. No overclock either :p

-I wrangled together some consonants and vowels and created this post-
[Nexus S Android Development] NPS_CA:
Getting the hang/black screen unresponsive power button but soft keys lit.

ADB DOES work - but logcat showed nothing useful. Trying to use Wakey droid failed as looked like the VM crashed hard. ADB reboot DID work.
[Nexus S Android Development] chrlswltrs:
I was very happy with RC4 until today. It had been running great, no reboots, no freezes, smooth, fast, etc. Today I went to work and noticed my phone in a bootloop, happened again later, then tonight my phone completely froze, all of which are unacceptable.

If I am with a customer sometimes I need to show them things using my phone and this is unacceptable. This could literally cost me hundreds on a single sale.

I just want stability. I really don't want to have to buy an iPhone for stability for customers and my Nexus for everything else
[Nexus S Android Development] MohamadKarbi:
I always liked the speed and options in cm. However, I believe modaco gr14 is very stable. I'm using it for long time and almost no issue except for the more options and tweeks I miss from cm
[Nexus S Android Development] amjb71:
Why would you use a RC, or even any non official rom on a phone used for work? I know thats not what you want to here, but it true, I love mucking about with my NS with different roms, but they can be buggy, as lovelymanmk says, modaco gr14 is very stable, but still, for mission critical work stick with the stock rom, or a second phone?
[Nexus S Android Development] phillevy:
This dim screen bootloop seems to be cropping up more and more and is the only real issue for me - with various versions of CM7 up until RC4. I have only used Netarchy kernels. Is it known yet what causes this or what is actually happening when the bootloop kicks in and whether it is ROM or kernel related?
[Nexus S Android Development] Kingken:
agree... had it 2 times 2 days... give up.. back to #26..
[Nexus S Android Development] phillevy:
What kernel are you using?
[Nexus S Android Development] dudeimgeorge:
Ahhhh.I'm scared. I stop cm since back in the pointless rc1 and some nightlies. Too much kinks. This rc4 has been splendid. Please don't happen to me!
[Nexus S Android Development] Kingken:
Was on netarchy 1.3.0..
[Nexus S Android Development] mortal300:
GMAIL problem cause of RC4?

I upgraded from RC2 to RC4. I did not wipe and flash. I just flashed RC4 like an upgrade. i did not reflash google apps obviously.

Now everytime I get an email. I open the email app and the email is truncated and is not expanding to the width of the phone. I have to tilt the phone landscape then tilt it back to regular portrait way and then the email contents stretch the entire length of the phone. (As opposed to stopping halfway thru the screen as if my screen was half size less.

Why is this happening :(?
[Nexus S Android Development] Arcarsenal:
Because it's a bug? Just rotate your phone and then rotate it back. And another bug: Just had another dim/inverted colors bootloop with #34 and Netarchy CFS 1.3.0.2. Seems to be quite frequent these days.
[Nexus S Android Development] RickROM:
Why are you modding your phone if you need it to be stable?
[Nexus S Android Development] zephiK:
^^ or using non-final release builds
[Nexus S Android Development] leoccc:
I full wipe but not use radio xxkb3 and install the rom,Got the com.google.process.gapps error and auto reboot.
[Nexus S Android Development] mortal300:
RC4 bug? yeah just wondering if its my phone only...
[Nexus S Android Development] 3Shirts:
I am still getting dimmed bootloops regularly still with RC4. They seem to happen overnight while charging which is a concern as I wake up to it not knowing how long it's been doing it. It's usually very hot though!

I am going to just turn it off overnight until the next RC or stable.
[Nexus S Android Development] :
I used to have that problem with my previous phone (N1). What I did is I use tasker to send me an email every time the phone reboots, that way I can track the stability of the phone easily. Also, when running in home network, I also do automatic logcats to see what caused the problem.
[Nexus S Android Development] 3Shirts:
The problem is that at some point it crashes and goes into the bootloops but the loop never gets into the OS so Tasker can't do anything. In the morning I wake up to find it bootlooping and really hot so have to pull the battery. Once I do that it seems to boot fine.
[Nexus S Android Development] Aria807:
I installed CM7 Nightly 29 on my cousin's HTC Desire. He says his phone never has any issues and hasn't rebooted on him. Not sure if there are any major differences in CM7 between the different phone versions, but I'm thinking there shouldn't be very much difference. If his Desire doesn't have any issues, then maybe it's something hardware/driver conflict w/ ours?
[Nexus S Android Development] Jayrod1980:
To those with the reboots, I would say when you wipe be sure to format system inside clockwork recovery. Seems bad stuff can get left behind if you don't. Also, I use a tpu case and the phone for me will not handle oc for long at all if plugged in and running anything intensive. Having said that, don't overclock with a case on. The phone probably just cannot dissipate heat regardless of your CPU handling the oc. I use ogdobbers kernel and I have no reboots. Stick to stock kernel or that one if you are getting rebooted with one of the other kernels. Sometimes the phone would freeze up on netarchy or morphic even without the overclock enabled. My phones been rock solid since doing these steps and that's with every rom I've tried.

If you've returned to stock including kernel after formatting system then I think you have a legit problem. If not, try those steps.

To those that get mad because they get reboots or freezes with a custom kernel or overclock and blame it on being a crappy phone or whatever, remember, you are running your phone out of original intended spec! They don't ensure stability in the device when pushed to a place the phone wasn't meant to go. Its like a high pressure Turbo car that you get upset when you push 100+ HP over stock and get upset when you blow your engine. It just wasn't intended to perform reliably in that condition!
[Nexus S Android Development] Aria807:
I do the steps specified in other threads regarding a clean install (like coming from stock -> CM7 with the wiping of phones system data and cache and dalvik).

Still gets the occasional dim bootscreen reboots.
[Nexus S Android Development] ogdobber:
guaranteed way to start fresh (btw don't restore apps, redownload them)

fastboot oem lock

then

fastboot oem unlock

this absolutely wipes everything including the sd card so backup your photos

I had reboots after alot of "test" things in the beginning. since doing this (about a month ago) not 1 reboot! of course the addition of 2.3.3 helped this...

Also I have ran as long as 3 days without charging (low use) with no reboots (voluntary or involuntary)
[Nexus S Android Development] dudeimgeorge:
Please Read

I can assure everyone when i say, after a few trials, NSCOLAB with RC4, properly wiped is flawless.

the reason why i say this is because i have exhaustivley tried, EVERY nightly RC and OC/UV kernels with nothing but issues: Bootloop, dim soft boot, mid phonecall boots, hard freezes, soft freezes, brain freezes, bank account freezes, horrible cocaine addiction, ..so on and so forth.

Everytime i have wiped (fastboot lock unlock, and for the hell of it, wipes and permission fixes) and put the new one back one ...and added..little by little..my apps...(yes i died inside, yes it sucked, yes its definently some type of OCD) so all problems that occured, was a real issue. however....every since i have done this stupid painful process on NSCOLAB rc4 (cant vouch for the plain rc4..which is ironic, that the hybrid works..but definently means both that kernel and this RC4 is great)

I HAVE NOT GOTTEN ONE PROBLEM AT ALL....(technically the 1.4 oc initially made me to a battery pull but there after i COULD have stayed at 1.4 but i dont....1.3..or 1.2 usually..NOTHING..NADA..ZILCH issues on the loops and freezes...

I will say tho one thing that has never been solved..just a personal irritant, but techinically this is inexcusable....in the gesture feature..using a contact to jump off from on the lock screen has still yet to be solved...TRY IT...try using a contact to go to off the gesture lockscreen.

anyways. laters but seriously, can we push up the gesture to a contact FC? i would love that have that to work
[Nexus S Android Development] Aria807:
I'm currently on RC4. If I do that fastboot oem lock and unlock, what happens? Last time I unlocked my bootloader my phone was still on stock 2.3.2. Will I boot up into a clean RC4?
[Nexus S Android Development] tmello56:
Anyone notice a decrease in battery life on the latest nightly? 26-RC4 had great battery life and 36 seems to be draining my phone a lot faster today.
[Nexus S Android Development] chrlswltrs:
Mine has been running great, battery has been good today. I just upgraded this morning from RC4
[Nexus S Android Development] chrlswltrs:
It will wipe everything on you phone including your SD partition and return to stock, at least that is my understanding, someone please correct me if I'm wrong.
[Nexus S Android Development] AndyCr15:
I'm assuming you can just remove your SD card, put it back in after. (I'm not asking will it still wipe the card while it's out... just that it wont error as there's no card or even try and wipe it when the card is put in afterwards?)
[Nexus S Android Development] Aria807:
Well when I was on 2.3.2 stock, I unlocked my bootloader and my phone was completely wiped, and I ended up back on 2.3.2 stock.

When I bought the phone, it was 2.3.0 and I had to update thru 2.3.1 and 2.3.2.

But now the case is I'm on CM7 RC4, so I am assuming if I lock and unlock bootloader, I'll be back on RC4?

I do want to wipe the SD portion since there might be stuff on there causing the dim bootloops.
[Nexus S Android Development] 3Shirts:
Good luck removing the SD card from a Nexus S :D
[Nexus S Android Development] jonjon68:
Just remove the SDCard huh? Me thinks you don't have a Nexus S.
[Nexus S Android Development] dudeimgeorge:
Hahaha

sent from my ****en Nexus S WITH AN SDCARD!...in my other pocket
[Nexus S Android Development] kemsiro:
Nexus with removable sd card lol
[Nexus S Android Development] erikwervo:
me insert 32gb sdcard but my nexus s wont detect.

damn.. its a simcard slot!
[Nexus S Android Development] AndyCr15:
Oh yeah, lol

Sorry, just so used to having SD card is all.
[Nexus S Android Development] gasparzim:
Anyone having problems with apps that need superuser?

Busybox does not install - Failure! /system/xbin could not be remounted as RW!

ADFree - Unable to locate a opartition to remount to write the hosts file to.

Looks like the partition is read only... anyone?

EDIT: I solved ADFree using "mount -o remount,rw /system" on terminal emulator, but busybox keeps giving me the same error.
[Nexus S Android Development] YDardeer:
I've been getting a lot of force closes with the CM settings lately, and in most cases it causes a freeze?? What's the deal
[Nexus S Android Development] Aria807:
lol there's still bugs in RC4. Granted it isn't nearly as bad as RC2. I just hope the finished product won't have any more dim bootlooping or phone freezes
[Nexus S Android Development] kemsiro:
Pretty stable for me. So far, no freeze nor bootloop.