yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] bgdxv:
Ok so i wiped battery stats, did everything and my battery still just charges to 98%. Is anyone else having this or is there something wrong with my phone? :( I have an i9023, not i9020.

Apart from this, everything else is working perfect. Thank you very much for your work cyanogenmod team
[Nexus S Android Development] suhas_sm:
Google apps fcs all the time :(

any suggestions ?
[Nexus S Android Development] saranyan:
I am not having any problems, Did you wipe everything and flash the latest Google apps?

Try fixing permissions in recovery.
[Nexus S Android Development] suhas_sm:
Yeah, I had wiped everything, flashed them from Rom Manager download version, Fixed permissions from RM and also recovery.

But in the end, I just uninstalled and then re installed them from market and now no issues.
[Nexus S Android Development] bgdxv:
So no one that has an i9023 can tell me if theirs charge to 100% with this rom? :( what's the point of a big community if no one helps each other?
[Nexus S Android Development] mapin0518:
Mine charges to 100% (I9020T).
[Nexus S Android Development] t3ej4y:
Obtaining Ip address Wifi problem:

After making a nandroid backup of my setup, I somehow seem to keep running into the wifi problem where it shows 'obtaining ip address from....' but never being able to connect. It worked fine for a while but seems very inconsistent now, does anyone know how to fix this?
[Nexus S Android Development] matt2053:
It has nothing to do with bluetooth, I have never used bluetooth on my phone once, and I have the same issue.

---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------

Reboot your wifi router :)
[Nexus S Android Development] mapin0518:
Figured as much, but just trying to provide as much info as possible about the circumstances when it occurred.

So what does it have to do with, do you know? I mean what's different about CM7 and all the other ROMs that don't have this issue? I suppose that's the million dollar question.
[Nexus S Android Development] saranyan:
After 55 hours of uptime i got a freeze today. When i woke up phone was just blank and had to do a battery pull.

Flashed Trinity TUV 10 to find out whether it's a kernel issue. Will post the results soon...
[Nexus S Android Development] darthchilli:
Does anyone's phone suddenly jumps to the messaging app out of no where and the search touch button just doesnt light up?

curious as this has been happening since I upgraded to 7.1.01
[Nexus S Android Development] matt2053:
That is the big question. All CM7 based roms have this issue. For Nexus S, only AOSP roms are not affected. This issue has been open in CM7 on Nexus S issue tracker for over six months (since April). I don't have any hope left and I have to use stock Rom now. :(
[Nexus S Android Development] tekkitan:
I have been running CM7 on my Nexus S and my Thunderbolt for a couple weeks now but I have not seen a freeze once. It has to be something you guys have in common...
[Nexus S Android Development] OkNewMedia:
Can't enter Recovery

Have CM7 Version 7.1.0, and I'm trying to update to the latest version through Rom Manager. However, after downloading the update, my phone goes to the fastboot screen, instead of into Clockwork mod recovery, and will not enter recovery, when I choose it from the menu. How do I get my phone to enter recovery mode?
[Nexus S Android Development] KalimochoAz:
Have you both folowed this?

1- wipe system default parameters

2- wipe data/cache/dalvik

3- flash CM7.1.0.1

4- DO NOT flash googlewalletfix_v5 !!!!!!

5- flash gapps-gb-20110828-signed

6- flash gapps-gb-20110828-newtalk-signed

7- reboot

DO NOT change kernel

DO NOT use taks killers

DO NOT recover backups

DO NOT change kernel parameters

DO NOT use or install SETCPU

Kalim
[Nexus S Android Development] saranyan:
I did that and i got a freeze after 55 hours. Randomly when i unlocked the phone , It just froze and had to do a battery pull.

Have tried flashing a different kernel....
[Nexus S Android Development] KalimochoAz:
Since this is not happening to me I need logs from your hangs to realize why this is happening. In general most people is reporting stability for this ROM so it must be you that are having issues who has to report about them, otherwise that kind of messages doen't help me to find a solution for your devices.

Kalim
[Nexus S Android Development] saranyan:
I was in college when it happened, Sorry, ill report with logs when it happens again.

EDIT:

My phone just randomly rebooted again, Have attached a log.
[Nexus S Android Development] mapin0518:
Yes I said I did in my original post FYI. I also ran zero 3rd party apps. I'm running stock GB launcher. And I posted the log for you as you had requested as well.

Kalim: you mentioned you don't have this problem... what's the longest uptime you've had? Just curious if you are running phone long enough since some reports are over 40 or 50 hours up uptime.
[Nexus S Android Development] joshthewaster:
You may need to reflash clockwork recovery. I had this problem when I tried to use rom manager to update my recovery it just got deleted.
[Nexus S Android Development] KalimochoAz:
Are you using launcher Pro? It seams a problem on launcher pro
[Nexus S Android Development] XxSilent22xX:
My phone also froze recently while using the voice app.
[Nexus S Android Development] iamkifo:
I am using Gentle Alarm on 7.1.0.1 and it froze the phone too. I am wondering if other alarm apps work well with CM7.1.0.1 too?
[Nexus S Android Development] saranyan:
Yes i am using launcher pro. Can that cause freezes and reboots??

I'll uninstall it now, Is there any way in which i can get Stock GB launcher to Cm7.1?
[Nexus S Android Development] matt2053:
I do not use launcher pro and I have the freezes and reboots. So I think the issue is elsewhere.
[Nexus S Android Development] :
Use my signature and get dark launcher. it's stock but transparant and darky.
[Nexus S Android Development] saranyan:
Thanks man, I have shifted to oxygen as of now. Will revert back to CM7.1 when i have the time and patience to do a fresh install. :)
[Nexus S Android Development] slimjimwoods:
any way to edit the touchkey timeout time? Ive checked in sys/class/ but there is no backlightdimmer file to modify...
[Nexus S Android Development] :
open a terminal window

su

echo 5000 > /sys/devices/virtual/misc/notification/timeout

For 5 second.

You can use with latest nightlies. #235 or latest version.

Don't do less than 1000 because accelerometer won't work, at least for me.
[Nexus S Android Development] slimjimwoods:
thankyou dude,
[Nexus S Android Development] :
You are welcome.
[Nexus S Android Development] dfl:
I uninstalled launcher pro, did a full wipe, re-install, default kernel and i am rebooting or freezing when i try and listen to music after 4 min. with WinAmp.

going to try the stock player and see if that makes any difference.

---------- Post added at 07:59 PM ---------- Previous post was at 07:32 PM ----------

So far its been playing 5 songs straight on stock music player. WinAmp would crash when changing song.
[Nexus S Android Development] darthchilli:
my battery's been horrible since I went back to CM7.1.0.1

running

WidgetLocker

ThemeChooser

Simiclock

SimpleCalender

Simifolders...

I whatsapp/tweet/LINE/txt a lot.

Use to be able to get 10-12hrs on nscollab...

someone help out a n00b?
[Nexus S Android Development] iamkifo:
Just to add on to the Gentle Alarm freezing on CM 7.1.0.1 report, i changed to Alarm Clock Extreme Free and it seems to work fine. The phone didn't freeze while the alarm went off on the charger.
[Nexus S Android Development] Harshwardhan:
had freezes [in NB228] after 90hrs or so up.

Then flashed 235 after wiping and everything, freezes after 20hrs or so.. just froze on unlocking, had to do a battery pull.

Back to boring stock for now. :(
[Nexus S Android Development] KalimochoAz:
On NB238 notification will be a little bit diferent. take note of this:

On notification LEDs estart to blink and

after 5 minutes of blink, LED stays ON all the time. If arrives

other notification, then LED blinks again so you are always

noticed of new messages with a new blink start

/sys/devices/virtual/misc/notification

led ( 0 no notif, 1 notification )

timeout ( time in seconds that after the screen is on, LEDs

will turn off. if 0 then never ) DEFAULT 0

blink ( 0 no blink support, 1 blink support ) DEFAULT 1

blinktimeout ( time in minutes to stop blink ) DEFAULT 5

version ( number of version ) V2
[Nexus S Android Development] art_sn00p:
In CM settings under Interface section --> screen effects

It doesn't make screen effects settings persistent. For example "calibrated N1". It lasts until reboot and after that no effect again.

Is this setting really impact battery perfomance? And how to make this setting persistent?

Don't like default color temperature in CM7 and my sLCD screen won't let me play with voodoo colors.
[Nexus S Android Development] Seikoom:
Does anyone else's sound toggle - sound+vibrate, not work properly? As in there will be a sound but no vibrate when a notification comes through?
[Nexus S Android Development] iamkifo:
Viber just froze my phone running CM 7.1.0.1. Removing it to see if the phone improves.
[Nexus S Android Development] DoktorZero:
CyanogenMod 7.1.0.1 + kernel franco, the perfect combination
[Nexus S Android Development] :
kill dsp manager for a while and try viber.
[Nexus S Android Development] belair56:
Works

Running the latest Kang, tested blink and time out, both work. :)
[Nexus S Android Development] KalimochoAz:
Next nightbuild will come with gamma correction resolved

Kalim
[Nexus S Android Development] :
This looks like the thread which is stable releases for. Not for nightlies.
[Nexus S Android Development] :
@Kalim Hi.

Not working "echo 1 > /sys/devices/virtual/misc/notification/bl_timeout"

Not working "echo 1 > /sys/devices/virtual/misc/notification/timeout"

or in device menu delay time not working too, if you choose 1 second or 2 or any of them and i guess this is beacuse of why leds on while usb plugged in.

Gamma things still same, when you touch the settigs r g b one by one it will be good but each reboot goes bad.
[Nexus S Android Development] KalimochoAz:
MYPaT If you have tested other kernel ? Some kernels changes LED notification library, so it will make your led system fail. If this is not the cause, check what apps are configured to make notification. there is a config to enable LED on plug USB and when you set default parameters, this option is enabled.

Thanks for notify the gamma boot issue. I have already solved. in 4 hours we will have a new NB and this is corrected there.

Kalim
[Nexus S Android Development] :
no i never change kernel too. :)

also i don't led option too i always all unconfigured setting change as force led off one by one. what ever it's not big problem forme but. bl_timeout not works with device settings with echo command too even with teminal emulator. Thanks.
[Nexus S Android Development] KalimochoAz:
What is the value of blink?

cat /sys/class/misc/notification/blink

blink should be 1
[Nexus S Android Development] :
yes 1 also it's 1 by default. believe me i do it since ezeekel implement and after your change too was timeout than now bl_timeout in /sys/devices/virtual/misc/notification

with #242 works good. i jump from #242 to #247 not working now with #249 not working.

Also as you said "check what apps are configured to make notification. there is a config to enable LED on plug USB and when you set default parameters, this option is enabled." there is nothing appeared inside the unconfigured section. as i said i cganged all settings for each application as force led of than save them and they all go to misc section automaticly than unconfigured setion dissappeared. after plug the usb nothing comes inside unconfigured also there is still no unconfigured section.
[Nexus S Android Development] KalimochoAz:
Try to find me on the irc and we will ckeck what happends. Here is working ok so I will need to see what happends on your device to understand it
[Nexus S Android Development] :
what server what channel?
[Nexus S Android Development] KalimochoAz:
at freenode #cyanogenmod
[Nexus S Android Development] :
people that who suffer from touch key back lithgs on while usb plugged in.

please open setting/cyanogen setting/interface/led interface open category than open edit category settings and led mode select use application settings than press flash test and ok button. everything will be work untill you reboot the phone. whe find this way with the kalim so thanks to him. :)
[Nexus S Android Development] steve.garon:
So I assume there will be will be a patch for this at some point?
[Nexus S Android Development] :
http://review.cyanogenmod.com/#change,9958

:)
[Nexus S Android Development] KalimochoAz:
Is not already patched. After the first boot fails but recovers normal behaviour on first notification.

Kalim
[Nexus S Android Development] KalimochoAz:
NB 251 will have this issue solved with LEDs
[Nexus S Android Development] :
if it wasn't about for 1 second it will be good to use it for 1 second.
[Nexus S Android Development] saranyan:
I have a general question,

I have tried CM 7.1.0 and CM 7.1.0.1 with the stock kernels, 7.1 got a freeze within the first day, 7.1.0.1 after four days.

Now i wish to test whether Cm is stable with Trinity TUV 10. So which version should i flash, Any feedback would be appreciated.

I believe the difference between the two builds is just BLN?

Can anyone confirm this?
[Nexus S Android Development] maxmax0:
CM 7.1 instability on some Nexus S is a well known but still unsolved problem.

I was in the same situation as you, sorry to say that I have tried various trinity versions but sooner or later the phone froze on me. Your best bet is to use another ROM or wait for Google ICS update.
[Nexus S Android Development] KalimochoAz:
The only I can tell you both is that I cannot solve what I'm not experiencing on my device. If you wanna cyanogenmod team to solve your specific issues the only way is to report logs in order to give as clues of what is happening on your mobiles. On the other hand if you prefer other ROMs there is full of them for this device and I have no problem at all with this.

Kalim
[Nexus S Android Development] maxmax0:
Logs are available in the issue thread that has been open since early June:

http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority

Also, please understand that mentioning/discussing this issue here does NOT mean that we do not appreciate your work, and it is not meant as criticisim at all. We are simply discussing an issue some people face and how to deal with it.

You guys did an awesome piece of work in any case and I just hope that one day this gets fixed.
[Nexus S Android Development] :
Ehi guys! I'm going to buy an european Nexus S (i9023), so the one with the slcd display...I'll be able to flash "stock" cm7 for the nexus s?

Thanks in advance!
[Nexus S Android Development] KalimochoAz:
If you read this issue thread, there is only one guy reporting a log afte 7.1.0.1. In the post I don't know if this log is done with this version or with NightBuild 223. If you read this log you can see there is intalled TitaniumBackup ( but has this guy recovered a previous backup? ) I see reports of E/ processkiller ( Is he using a process killer app!!!! NEVER USE SUCH APPS ON ANDROID !!!! )... and so on... So I cannot debug this.

The reported issues on 7.0.3 are already corrected, so I can make more with this data.

I don't take this as a you don't appreciate my work, I just try to make you ( having isuues ) understand that I need information in order to have all devices working without problems. Since I can't repeat issues on my device, is working well also on NB, I can solve the unknow bugs.

Kalim
[Nexus S Android Development] KalimochoAz:
yes, no problem at all
[Nexus S Android Development] caliban2:
maybe have a look at ezekeel's sources, his is the only custom-kernel i get absolutely no stability-issues with on cm7.

i should also note that with cm7 "stock"-kernel sod happens less often (up to 48hrs), while with Franco's & morfic's the phone rarely managed to run 12 hours. what they all had in common was once the first sod happened, frequency went up significantly. (4h, 1h, right after reboot - everything was possible)

if i read his first post correctly, ezekeel is using newer sources?
[Nexus S Android Development] saranyan:
I have managed to run CM 7.1.0.1 for 55 hours without any issues, But it froze after that. I know ppl who got freezes after 5-6 days, So you should atleast test CM for a week or two!
[Nexus S Android Development] caliban2:
i come from the x1 - we had to deal with unexplained sod for over 6 months. so yes, i know it's too early to claim it stable. :)

but my settings, my apps (sync) and my usage-profile haven't changed a bit. and yet i had no sod, no fc, no reboot - that's a good sign. none of the other kernels made that possible.
[Nexus S Android Development] crump84:
I recently rooted my girls Nexus and put the latest CM7 stable on here phone. Is there a known reboot bug with the stable? I got *****ed out this morning cause her alarm didn't go off because here phone was stuck on the boot animation. :/ if this is a known bug, has it been fixed with the latest nightly? As of today what would be considered the most stable nightly? Sorry for the questions but since its not my phone is have a hard time troubleshooting. Thanks for any help
[Nexus S Android Development] :
Thank you!
[Nexus S Android Development] mapin0518:
She should probably just stick to stock which is most stable. Yes there is a reboot bug that affects some people more than others. I have to do a battery pull once a day on average.
[Nexus S Android Development] nyijedi:
CyanogenMOD has NEVER been stable on the Nexus S. I've dabbled in official releases, nightlies, and RCs since it was first released for the Nexus S, and it has always had random freezes, reboot, and boot loop problems. I wanted to use it on my Nexus S - I really did -- but it's just not usable for anyone who wants a stable experience. I recommend using Peter Alfonso's Bugless Beast. I've been running it for a few months and have literally not had a single reboot, freeze, or boot loop. It's very refreshing after months struggling w/ CM.
[Nexus S Android Development] steve.garon:
Try nightly 242 with my kernel. Havent had crash, sod or any other bugs for the past 2 weeks.
[Nexus S Android Development] terryhau:
Hi KalimochoAz.

Just did a clean install of 253. The CrespoParts settings still doesn't load proper defaults when it has never been set before. Color multiplier and gamma settings are all maxed out, and all voodoo sound settings are enabled (some are undesirable, eg. mono downmix). Can you add in the default settings and maybe an option to restore default color multipliers/gamma.

Thanks.

BTW. If you want all default voodoo settings without installing voodoo control, or you want to use the voodoo control instead of CrespoParts, you can delete /system/app/CrespoParts.apk.
[Nexus S Android Development] KalimochoAz:
I take a look. It is suposed to have gamma defaults recover, I change the other settings and look at gamme to see what happends
[Nexus S Android Development] MultiCulti:
:eek: don´t agree ... running CM 7.1.0.1 with franco.kernel ... and since i stoped playing around with the voltages and xtrem overclocking, i NEVER had any freeze or reboot!
[Nexus S Android Development] saranyan:
Did you have weeks of uptime without any issues?
[Nexus S Android Development] MultiCulti:
@ least 2 weeks ;)
[Nexus S Android Development] maxmax0:
Good for you - however doesnt change the fact that CM is not stable on Nexus S for many people.
[Nexus S Android Development] MultiCulti:
yes thats rigth, BUT as i can´t say, CM is stable for all, cause it´s stable for me, others can´t say, it was NEVER stable for all ... just because he having problems with it! ;)
[Nexus S Android Development] HeavenlyWinds:
Cm stable isn't stable at all, if i had to choose between nightly and stable, i would choose nightly.
[Nexus S Android Development] matt2053:
Listen, some people are going to say try this kernel or try this nightly and I never had a problem and blah blah blah. But the fact is that for many, many people, CM freezes or gets stuck in a reboot animation from time to time, and it often happens overnight, and if it does, the alarm won't go off.

If your girl relies on her phone for her only alarm, then CM7 is not an option for her on this phone. Sorry. I have the exact same problem. My phone is my only alarm clock so I can't use CM7 either.

http://code.google.com/p/cyanogenmod/issues/detail?id=3850

http://code.google.com/p/cyanogenmod/issues/detail?id=3459
[Nexus S Android Development] maxmax0:
well if too many people have issues with it, it ain't stable.
[Nexus S Android Development] KalimochoAz:
http://code.google.com/p/cyanogenmod/issues/detail?id=3459 : Since 7.1.0.1 the only reported error with a logcat is after installing ICS g+ that of course is not compatible and makes a lot of issues to the ROM.

http://code.google.com/p/cyanogenmod/issues/detail?id=3850 : here you have 2 error logs since 7.1.0.1...

1.- http://bit.ly/vRkHL0 : I/ActivityManager( 211): Process com.keramidas.TitaniumBackup (pid 13978) has died. If this has a backup recovered into the ROM, is normal that behaviour ( I'm not sure if this has been done, but normally when I install an app is to use it )

2.- http://bit.ly/vlKkzM : I can't see any fatal error there.

With this I'm not saying there is no issue on CM stable, for me and for many other users is stable, but since I don't use some parts of my device regularly, it can be issues that I have never experimented, that the reason of this CM reporting page.

What is important when you report on this page is what is asked for in the first commit. Version, backups, root apps, logcat, dmesg... that will help me to really find this issues where can they come from and try to solve them.

Thanks for understanding
[Nexus S Android Development] simms22:
i have not a single issue with cm. i understand that i dont have long uptimes, i flash frequently. my question is why do people have such long uptimes? you want to reboot manually every once in a while, preferably once a day. it will keep your phone running at its peak/best. dont say that you dont have time for a reboot, because thats just bunk, everyone has time for a reboot. ill repeat it again, reboot your phones once a day, you will be happier with it.
[Nexus S Android Development] Roscopcoletrain:
Doesn't always help though. For example I went almost a week without an issue. Then the other day I woke up, phone was in dim reboot. I did a battery pull. Did some stuff and rebooted again. 2hrs later it dim screen rebooted again.

Point is, it just seems so random.
[Nexus S Android Development] Jnewell05:
Freeze then Reboot after trying to play a 5min long video that i recorded at a concert though gallery twice back to back. And slower then stock Android. Didn't get anything from logcat to report.
[Nexus S Android Development] caliban2:
sure, 7.1 has stability problems. but they are very hard to trace... :D

since i switched to glados-kernel (1 week ago?), its almost stable. longest run i had were 3 days, something i couldn't achieve with cm-kernel or any custom-kernel (always 24 hours max, and once the first freeze had happened, they kept coming by the hour). so i can say that kernel did something good.

so far i had to pull the batt 2-times:

- sod while charging overnight

- total freeze on lockscreen

i always get reboots when using bfs-kernels, but never with cfs - at least that i can trace. regarding logcats for the upper two cases - I'm trying, but the damn phone doesn't want to sod when i pull one! :D (sod was with glados 1.3, may be that later versions fixed something. lockscreen-freeze happened yesterday with 1.5, after the system was up ~36h)
[Nexus S Android Development] maxmax0:
yeah you could be right, i may just need to start doing that. cant say i really like the idea though.