yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] mih_:
calendar fc

It works also for me.

If i take calendar.apk from latest 2.3.1 build and put it to /system/app/ then calendar stops fc.

But, since it's for 2.3.1, it has some side effects, like missing titles and shifted headers in week/month views.

I hope, they'll fix the calendar 2.3.2 itself somewhen.
[Nexus One Android Development] mikebeatrice:
Maybe since it's so easy to flash these things, people are forgetting the big picture...

The OP makes it pretty clear that these are early builds that aren't for the average user... things could be broken... or incomplete. Wait until the RCs if you want it to be more stable.

These builds are meant to test out what's coming in CM7 and help provide feedback on what they can work on to improve it before it's done. Not that something like CM is ever "done"....

I'm sure if the call freezing thing is something they're causing (so far I haven't experienced that and I've been flashing every other build since #3), they're working on it for CM7.0 final.
[Nexus One Android Development] fitsnugly:
Amen! Too bad this idea will be lost after a page or so and everyone will be complaining again. :rolleyes:
[Nexus One Android Development] k3vink3vin:
I was not able to pick up the first phone call I received after flashing #19. The phone was ringing and caller ID was shown on the screen, but the slider to pick up isn't there, no buttons work either so there was nothing I could do except looking at the phone.

All is normal again after it stopped ringing.
[Nexus One Android Development] BritSwedeGuy:
I didn't have it with the earlier nightlies, then I had it for a couple of them, now with 17 apparently it's gone again.

I did a FULL wipe, flashed ROM, signed in, let it settle, rebooted to flash gapps, allowed automatic app restoration over WiFi.

Also the problem with apps moved to SD (built-in, not DT) not being seen in the Market "My apps" have gone.
[Nexus One Android Development] daveid:
I think some people confuse discussing issues with the rom with complaining. And, in case you weren't paying attention, this is the place to discuss issues with the rom.

Now, what people shouldn't do is expect to get any kind of support (other than possible confirmation that others are experiencing the same issues) beyond the usual XDA dismissive attitude. I think this is where the real problems come from. People expect a better answer, or someone to be kind to them... well, this ain't the place for kindness - sucks, but it is really the truth. So, when someone responds with the usual "Read the OP, no support, no bug reports, is not even an RC there are going to be bugs - deal with them", etc. it really does nothing but breed the contempt and rage that have come to be associated with new users to XDA who were not expecting such a harsh community.

Just remember, the OP states "This thread is reserve for nightly build of @Cyanogen Mod Rom for HTC Nexus One

You can report and discuss all issue you are having with nightly build here."

So, for other users to come in here and tell people that they should just keep their mouths shut about issues they are having, it is contradictory to the OP/thread. It may sound like complaining (especially for those who sit upon a high horse judging everyone else who is not as experienced as them), it may not be constructive, however - IT IS THE PURPOSE OF THE THREAD!

/rant off.
[Nexus One Android Development] fitsnugly:
Apparently you have some sort of issue with me. Take it to PM, or simply hit that nice ignore button. Excuse me for not wanting to sift thru pages of people coming in here who don't search/read the post and whine/complain (once is issuing a report, multiple posts about the same thing is complaining). Now get off YOUR high horse about how other people should act as well, we all are entitled to our opinions, whether you like mine or not.
[Nexus One Android Development] imfloflo:
WARNING off topic
[Nexus One Android Development] mih_:
as a workaround, you can try to install any small app from market, and get "my apps" back.

it works for me at least, but sometimes it repeats after reboot :-(
[Nexus One Android Development] onesavior:
Previous versions I had to reset my ringtones and notification sounds, latest build seems to have fixed that, Just letting people know in case they had the problem.

Also, anyone know why after I flash a new update, reboot, my phone goes straight to edge? I just go and reset my network, And it goes into 3g, not a big deal, Just wondering if anyone else gets it, I had the same problems on cm6 builds as well
[Nexus One Android Development] Smokeaire:
Give my above suggestion a try. Can't hurt, might help.
[Nexus One Android Development] Disfigured:
When you say "reset my network", what do you do? Just toggle Airplane mode? Or do you go into network operators in settings and reselect your carrier? I'm not sure I have this issue, because most of the time when I reboot I am at home and connect to wifi, but I sort of suspect that this happens because sometimes i notice it flash "Edge" just before wifi connects.
[Nexus One Android Development] BritSwedeGuy:
I still had the apps I hadn't moved to SD under My Apps.

Also widgets weren't accessible for moved apps and account details (e.g. Facebook and Twitter) would be lost.

Thankful for anything and everything the Cyanogen team give me - not complaining! :D

Now flashing 19 - because it's 2 better than 17!
[Nexus One Android Development] asainz320:
I found the real solution to be wonk free!!!!!!

DON'T TALK ABOUT IT!!! JUST IGNORE IT!!!

I was wonk free for 2 days straight, not one wonk at all. Yesterday after i mentioned it... bamm! Mr. Wonk is back!! Now im flashing #19 to see if it helps.
[Nexus One Android Development] fitsnugly:
^^^^ This. I find myself testing for it entirely too often. It hardly ever happens with real world use for me...
[Nexus One Android Development] YettaVR6:
I had this same issue with #18 last night. Wasn't a big deal because it was someone i didn't want to talk to anyway :D

Only other problem i've had with the phone was one time I answered a call and the speakerphone was on for some reason. I think that was #16.
[Nexus One Android Development] masterpfa:
+1 to that One day maybe people will try to read the first page first and not just skip to the last page and complain, how about contributing with feedback?
[Nexus One Android Development] asainz320:
Just press the power button to turn off the screen and press it again to turn it back on and you'll see the slider :)

Thats what happens during a wonky call. The phone freezes and you can hear the other person in speaker mode for exactly 22 seconds, count it and you'll see im right :confused: wierd!!

What i've done is tell people who call me the most to hold on the line for 25 seconds after they stop hearing the ring. :D
[Nexus One Android Development] temasek:
I would think posting of bugs or issues are fine. In the post context place emphasis on discussion rather than venting frustrations or demanding that the bugs should be top priority to be resolved, etc.

I believe CM TEAM knows exactly what they are doing. They actually do not need to release the nighlies but let us wait till RC or stable. But they did and it is a known fact that nightly build will have issues that need to be resolved.

A later nightly build may break something that an earlier build doesn't. For those can't take such issues perhaps good to revert back to CM6.

For all the wonkiness issues I believe you guys made your point and its time to let go and let CM TEAM get the issue resolved.
[Nexus One Android Development] Part Four:
Anyone else having touch screen issues with these nightlies? Particularly when using the car dock? Every 3rd or 4th time I dock my phone in the car, the touch screen starts misbehaving in such a way that most screen presses are registering about 1/2 or 1 inch below where the actual contact is made. Very frustrating and only resolved with a reboot.
[Nexus One Android Development] krumb:
I can't speak from using the nightlies (I prefer not to), but I can confirm that the touch screen does get wonky after being on the car dock for a few - this happened on CM5, CM6, stock froyo. I'm attributing it to heat...
[Nexus One Android Development] Gilg@mesh:
DSP Settings

what values do you guys using in DSP? I just enabled DSP (all values +0,0dB) and when I got a message it sounded ****ed up :/ and the DRC Ratio and HVRE, should it be on or off?
[Nexus One Android Development] MontAlbert:
Couldn't agree more mate- lilhermit has done an awesome job with first the hack and now his app. I donated to him before he had the app and also bought the app to support him.
[Nexus One Android Development] MontAlbert:
it all sounded ****ed up to me- i was using BT headphones and couldn't be bothered playing around with it too much but at this stage it sounded clipped even with small increases...

disclaimer: i am certainly NOT an audiophile!
[Nexus One Android Development] RogerPodacter:
when the touch screen registers 1/2 inch below your press, you just have to lock then unlock the screen and it fixes/resets the problem is gone.
[Nexus One Android Development] whoisthedrizzle:
The DRC shouldn't be used at all really. You don't add that sort of compression to a final product (being the track you are listening to) and there's no make up gain or preamp anywhere that makes it worth using, unless you like your music completely squashed AND softer. DRC decreases the dynamic range giving you more room to boost gain before clipping. HVRE may or may not make your headphones sound better, it is just adding adding some reverb and digital delay to one of the channels to try and compensate for a weird acoustic occurrence. You just have to trial/error with it really.
[Nexus One Android Development] uoY_redruM:
I second that.

Always fixes the issue for me as well. Generally happens when it gets too hot (GPS navigation mainly).
[Nexus One Android Development] pwig:
New nightly up. 08032010
[Nexus One Android Development] massari90:
Set cpu fixed in latest nightly
[Nexus One Android Development] Part Four:
Ah, ok. I don't recall it happening before the NB's, but it might have something to do with the fact that we're just now hitting the hottest days of the year.
[Nexus One Android Development] El Daddy:
It seems surface dithering is broken in the newest nightly. I have a lot of banding when swiping screens.
[Nexus One Android Development] uoY_redruM:
Well...I found another site you cannot bookmark lol.

Wildmonks kernel mirror page...it force closes when trying to bookmark.

Anything new with the newest nightly?
[Nexus One Android Development] Part Four:
Cool, thanks. I'd be surprised if I haven't tried that, but I can't say for sure, so maybe I haven't. Hmm.
[Nexus One Android Development] NguyenHuu:
i can confirm that i randomly get the touchscreen bug too once in a while. the fix, i turn off the screen then turn back on and it resets. it is not super annoying, but it would be great if it is fixed haha.

Someone already posted that new nightly is out, but here is the link: http://mirror.kanged.net/cm/nightly/passion/cm_passion-08032010-001250.zip, http://mirror.kanged.net/cm/nightly/passion/cm_passion-08032010-001250.zip.md5sum.txt
[Nexus One Android Development] uoY_redruM:
Hmmm, when I flashed the new nightly, I got the message (in the installation process) Welcome to CyanogenMod Nightly 0803blahblahblah but as it scrolled down it stated 0802blahblahblah and it also shows 0802 nightly on the about phone.

Perhaps just forgot to change the text?
[Nexus One Android Development] Goonish:
Yeah same here. Happens quite frequently nothing to worry about.
[Nexus One Android Development] Part Four:
Corporate sync certificates still funky on the latest nightly. Also, the in-call phone notification panel color is still stuck on white. It's pretty clear that they have no clue that the phone notification bug is there. Too bad there's nowhere to officially report bugs in the nightly builds.
[Nexus One Android Development] rickytenzer:
What was wrong with it previously?
[Nexus One Android Development] massari90:
When you reset the phone the clock speeds don't change to whatever you set it to previously. Had to do it manually. I think it was an issue with super user 2.2
[Nexus One Android Development] onesavior:
I reselect my carrier. Click on at&t then click T-Mobile...works every time...just annoying. I flash updates from him and or work...I rarely use wifi at home
[Nexus One Android Development] EnhancerFIN:
I resolved the wonky call issue.

Nexus One has got a new feature, (to stop Nexus S owners from bragging), with CM7, to know whether you really want to talk with the person calling you, or who you are calling to.

It may seem weird, and "wonky" but while screen is black and you are waiting for the call to start, think whether you really want to talk with him/her. You don't, and Nexie knows it, so it saves you the trouble. Also phone bills go down.

Case closed, next commit?

:D
[Nexus One Android Development] jerrygo2:
In CM7 build lock screen confiuration menu is seperated from others. I really want to add config for changing lock screen wallpaper. :-)
[Nexus One Android Development] jhenson496:
:eek: That's next generation stuff right there..... :D
[Nexus One Android Development] asainz320:
:D nice one!! but unfortunatly the phone bill is going to stay the same cus the call is still running even if your not able to talk, so is actually costing you more money cus it is 22 seconds that you're loosing out on. lol
[Nexus One Android Development] EnhancerFIN:
But that is just to tell the other person the fact that he/she is no longer wanted, and the savings come in the long run.
[Nexus One Android Development] asainz320:
ha ha ha :D i guess!
[Nexus One Android Development] k3vink3vin:
I am not entirely sure on the missing titles, events from Google calendar seems to show but not for events from other sync accounts.

Headers in week/month views seems to look fine here.

Hmm I can't upload the screenshots here via tapatalk for some reason.
[Nexus One Android Development] jangomango:
Just had a wonk...
[Nexus One Android Development] SiNJiN76:
This iás new. Automatic bookmarking when you press bookmarks (you don't have to press add bookmark in the bookmarks page...it's already added)
[Nexus One Android Development] Chahk:
Ok, guys gotta stop wonking all over this thread already. Damn wonkers.
[Nexus One Android Development] jangomango:
To be fair this was the first wonk I have had since I flashed..
[Nexus One Android Development] fitsnugly:
Sorry, it had to be done.
[Nexus One Android Development] drive2droad:
Feels this way actually
[Nexus One Android Development] xguntherc:
So anyone figure out what needs to be removed from the themes so they don't break the new status bar?? #19's changes to the pulldown widgets is causing it.

I'll just have to remove that part from my theme for now I guess.

Also, after clearing data on Voice Search I still get the occasional freeze with Voice. and this morning the freeze caused a soft reboot that never finished, resulting in me needing a battery pull.. it may be full wipe time. Haven't done that in MONTHS!
[Nexus One Android Development] temasek:
Okay

Each member is entitled to at least a wonk. Pls queue up...............next pls

lmao ;)
[Nexus One Android Development] baseballfanz:
For those that never get the wonk, if you want one let me know.

I have plenty to go around.:D Sharing is caring.:D
[Nexus One Android Development] makelegs:
I guess, when it comes to cm7, you're either a WONKER.... or a WANKER....? ;)

Sent from my Nexus One
[Nexus One Android Development] jacka$$1:
Never had a wonk since build #3 (first build). I'm now on build #19. Still no wonk....and don't want one. No wifi issues, BT issues, 3G issues, GPS issues, SD card issues. Nothing! Yaaaaay...go me! :D

But seriously...here's a tip. For every major iteration of Android (Eclair to Froyo...Froyo to Gingerbread...etc), do an absolute complete wipe of everything. Redownload all your apps (only once when upgrading to a major revision, no need to do it on every nightly). DO NOT use Titanium Backup (it's never 100% reliable).

On incremental updates (aka nightlies) just need to do a cache/dalvik cache wipe before upgrading. No need to redownload your apps.

Lastly, don't be f***ing lazy. DO NOT bother with ROM managers (they'really aggravating & suck donkey ass & not 100% reliable ). Do it manually via RA or CW. You'll save yourself from a ton of headaches.
[Nexus One Android Development] dtosun:
I m on build#19, there is no wonky
[Nexus One Android Development] NikNexus:
Has anyone been able to successfully add the Battery Percentage mod to CM7...im currently on the newest build #19, if anyone has the Battery% working please share with me =]

I've tried flashing some of the other ones listed in the thread but nothing is working correctly...all the problems ppl list are the ones im getting, and i've tried EVERYTHING!!!

So if there is anything anyone could post to help a brother out it would GREAT! thanks
[Nexus One Android Development] xguntherc:
Just to confirm. Is anyone having issues with Voice Search Freezing??? It freezes similar to the phone issue, and my capacitive buttons stay lit, screen turns off. and it stays like that for about 3 minutes.. This happens usually at least once a day.

Is anyone else having Voice Search Freeze issues? or is it isolated? if so i think I'll do a wipe on the next nightly. I've not wiped in a long long time. Since before FroYo!
[Nexus One Android Development] baseballfanz:
Try and clear DATA for Voice Search (in Manage applications)

Had that happened a few build back and clearing data solved it.
[Nexus One Android Development] xguntherc:
I've already tried clearing Data.. did not work. I'll try uninstall and reinstall right now actually. See if that helps.

Edit* Success, so far my Voice Search has not froze once. I've rebooted twice and tried it about 5 times and it's not froze yet. The real test will be after I flash tonight's nightly and then try. Cuz usually the first time is when it happens. Hopefully the reinstall fixed this.
[Nexus One Android Development] triciopa:
I understand, sometimes there are things that just have to be done
[Nexus One Android Development] laslow:
I've had the phone wonkiness for ages, tried all of the suggested fixes, and the Big Three Radios (4.06, 5.08, and 5.12), all with no luck. At this point, I'm willing to chalk it up to an issue caused by not actually having the proper proprietary files for the N1 from Gingerbread. As such, I think it's a pretty safe bet than when the official GB update finally drops and we can get our mitts on those files the issue will likely disappear....
[Nexus One Android Development] rickh925:
Sweet...I guess it is time to do the big double nuke wipe. It's been a while since last time (CM5 I think).
[Nexus One Android Development] baseballfanz:
I think it's more to do with a conflict somewhere in CM settings.

The Leo's and Micromod's GB ROM does not have this "feature".:D

I haven't tried nazorfox's ROM to see if it does it or not
[Nexus One Android Development] cmarti:
Get a set of Klipsch headphones. They are so superior than most others.
[Nexus One Android Development] mih_:
calendar fc

i've reproduced exact conditions for the crash:

- create any appointment and calendar app;

- add your own address and some like foo@bar.info (arbitrary addresses also works almost always)

- press "done", and reopen an appointment;

i'm getting 100% fc.

can someone please repeat the steps to confirm?
[Nexus One Android Development] aiewolf:
@cmsrcpackages_apps_Phone/gingerbread - Rabendra Patel * 01cff8 - Fix for Screen Blank issue when accepting call.... http://bit.ly/gnogGi

Fix for phone wonkiness appears to have been submitted
[Nexus One Android Development] baseballfanz:
Why wait when you can try it now?:D

Use Fitsnugly's ROM, it's already in it.:D
[Nexus One Android Development] xguntherc:
excellent. I'm glad this was finally figured out.
[Nexus One Android Development] baseballfanz:
I think that is to address a different problem. I still have the wonk.:D
[Nexus One Android Development] rickytenzer:
It hasn't been built yet.
[Nexus One Android Development] temasek:
Well one bug disposed and more to kill....
[Nexus One Android Development] fitsnugly:
Giggle. :p
[Nexus One Android Development] britoso:
on #19, no phone wonkiness now, or on any version prior :P
[Nexus One Android Development] temasek:
Not officially but was built by yours truely, fitsnugly ....
[Nexus One Android Development] mtw4991:
The little people that live in my phone built it for me awhile ago... look a couple of posts up and you'll see :rolleyes:
[Nexus One Android Development] rickytenzer:
Ah didn't notice. Sorry
[Nexus One Android Development] Androith:
I wonder if some day Google will bring OTA 2.3 to nexus ... or forget or wait for 2.4.

In any case, it is
[Nexus One Android Development] baseballfanz:
Yes either way something got fixed.:D
[Nexus One Android Development] temasek:
Ooooooo just saw its offically merged. Should be in upcoming official build.
[Nexus One Android Development] 66o6o:
Confirmed. but i'm on build 15.
[Nexus One Android Development] temasek:
Tip

If your screen hang due to whatever reasons you may try pressing power button and trackball at the same time. A menu will be shown and u can navigate using trackball and perform reboot, shutdown, etc.

Doesn't always work for u but worth a try.
[Nexus One Android Development] temasek:
Build 20 compiling too long. Hope it drops .....
[Nexus One Android Development] xguntherc:
yea.. usually here by now. lol
[Nexus One Android Development] phewizzo:
Buildbot definatly seems stuck at 16 minutes.

Sent from my Nexus One...
[Nexus One Android Development] temasek:
For almost 2 hrs.
[Nexus One Android Development] DumbUglyDragon:
Still nothing? :(
[Nexus One Android Development] baseballfanz:
Nope, buildbot seems stuck, need some grease.:D

That's gonna be one long waterfall.:D
[Nexus One Android Development] momomok:
It's been 3hrs

buildbot hanged?:D
[Nexus One Android Development] asainz320:
i dont know about #20 but i've been using #19 and it seems that the wonk is gone for good!!
[Nexus One Android Development] temasek:
Don't remind me. I've been starring at the waterfall every 15 mins or so. I'm itching for a flash now. :p
[Nexus One Android Development] baseballfanz:
I'm gonna flash some kernels just to get my hands from shaking.
[Nexus One Android Development] cmarti:
Haha! Junkie
[Nexus One Android Development] temasek:
Then why are u here?
[Nexus One Android Development] cmarti:
Awaiting for my fix!
[Nexus One Android Development] DumbUglyDragon:
The first steptl to recovery is admitting you have a problem....
[Nexus One Android Development] temasek:
I rather not reply him.
[Nexus One Android Development] baseballfanz:
Look like we waiting on #21 now.:D
[Nexus One Android Development] temasek:
Waiting patiently......
[Nexus One Android Development] neoxz:
building ETA in ~ 32 mins. What time is it now?
[Nexus One Android Development] cmarti:
It's 11:40PM in Florida.
[Nexus One Android Development] drive2droad:
I woke up shell shocked to see no new nightly build , is an RC on the horizon
[Nexus One Android Development] temasek:
Build 21 coming in 10min ++

You are on time.
[Nexus One Android Development] baseballfanz:
Build #21 waterfall look like a syringe to me.:eek:
[Nexus One Android Development] goTouch:
Already downloading 21
[Nexus One Android Development] temasek:
Forgotten I have cm notification. Acts as an alarm. Lol
[Nexus One Android Development] baseballfanz:
My notifications stopped working after build #14:(
[Nexus One Android Development] alapapa:
Look at all you gosh darn addicts!

flashing now! :P
[Nexus One Android Development] momomok:
Downloading. Hope it fixes the phone issue ...
[Nexus One Android Development] blahbl4hblah:
I can just wipe cache and dalvik over nightly #19 right?

Do I have to reflash darktremor's a2sd?
[Nexus One Android Development] triciopa:
WRONG!! the first step to recovery is holding trackball+vol down+power (he he he)

ok ok bad one but i'm just waiting for the download to finish!