yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] daveid:
There seem to be issues with Clockwork Recovery right now restoring a backup, to avoid them re-flash the ROM you were running when you backed it up along with the same g-apps. This will result in a working recovered backup, otherwise some permissions get fubared and you have seen the results.
[Nexus One Android Development] net.cat:
Sori guys but I can't really find the media volume settings, neither in audio menù nor cyanogen's audio panel!!
[Nexus One Android Development] Mozelstein:
Thanks.

I got RC2 flashed w/ a wipe and fresh gapps and everything seems OK now.

Are people just using older versions or CWM or has everyone moved to an alternative (Amon) ?
[Nexus One Android Development] daveid:
I just follow the procedure I outlined above for right now. I tried Amon, but since my trackball doesn't scroll downwards anymore, it was too difficult - an since Clockwork lets me use the volume buttons, I am willing to workaround this bug till they fix it.
[Nexus One Android Development] temasek:
Setting -> Sound -> Volume
[Nexus One Android Development] Basil 123:
Posting that twitter comment from Cyanogen was really encouraging, thanks.

It would be interesting to know what comes up in the dissection of this total PITA flaw in a ROM that was really very nearly perfect some time back.....

Once it's certified wonk-free, that fact really should be posted up in this thread's header IMHO....
[Nexus One Android Development] maedox:
Yes. :p

*******
[Nexus One Android Development] katiepea:
is that included in a new nightly? i flashed that from another thread, i agree it looks to be an improvement in the display, some will say it's too warm/yellow, and it might be a bit, but overall it's loads better, crisper edges and probably helps battery. it looks close to 6500k. i love it.
[Nexus One Android Development] uoY_redruM:
Flashed new nightly...again lol. Looking good!
[Nexus One Android Development] harmohn:
Yep sure is!...Oh and I tend to agree with you it possibly being an improvement on battery.
[Nexus One Android Development] hahahaa:
yes, loves this feature! monitoring the battery usage :) thx!
[Nexus One Android Development] metallicant:
New nightly just posted!!
[Nexus One Android Development] daveid:
Yeah, about ten posts too late.. ;)
[Nexus One Android Development] :
Yup its included in the latest nightly, I can flap confirm its a little too warm. I have calibration software/hardware and calibrate my monitors.

You have to keep in mind though, with a phone you will never have control over surrounding light. Light that has a huge impact on screens.

I is better use of the render effect though. Maybe they should have different presets for different temperatures.
[Nexus One Android Development] metallicant:
Sorry forgot to refresh... lol
[Nexus One Android Development] irishrally:
I'm really not liking the calibrated N1 colors. I definitely think it's too yellow and looks much better without it. Maybe I have a bad eye for the perfect coloring, but it just doesn't look right (the gray status bar barely looks gray anymore).
[Nexus One Android Development] uoY_redruM:
How long did you use it for?

When I first set it, it looked horrible. I used it for about 30 minutes and I'm loving it now. It slowly adjusts (visually).

I think its a LITTLE too warm, but I like it.
[Nexus One Android Development] :
That has more to do with the quick change of colors in a short span of time.
[Nexus One Android Development] irishrally:
Yeah, you're probably right, I only used it for a couple of minutes. I try out it for a little longer.
[Nexus One Android Development] shorza:
We are about 10 hours in front. :)
[Nexus One Android Development] shmigao:
that should be right. I think the builds are based on GMT (greenwich mean time)
[Nexus One Android Development] nonameduck:
Does the newest nightly still have the map issues?
[Nexus One Android Development] storm99999:
Oh, wow, I didn't know so much discussion went into my calibration here. I'd only been paying attention to my thread off in yonder distance...

Anyways, I think I'm going to greatly expand the capabilities of the render mode code. I plan on making an app so that calibration can be changed on the fly and it will load calibration on boot. 'Tis a shame that I can't do much better than whitepoint correction, but to me it's worlds better.

As for it being too yellow, that's because I'm basing it off of my phone. It seems that the average display is around ~8200K, but mine is 9300K. Didn't know that until a few minutes ago. I'll make some presets at the very least if I don't get work on more advanced features in in a few days.
[Nexus One Android Development] irishrally:
I definitely like the idea. I just need to get used to it I suppose or maybe some tweaks if my phone is cooler to begin with.

Does it lower overall brightness if you just lower blue and don't raise other colors? *exposes lack of understanding probably*
[Nexus One Android Development] shmigao:
me yes. but now clearing data allows map to open directly in the app drawer by clicking on map. prior to this build i had to take the detour via Places
[Nexus One Android Development] Marine6680:
Yes it is too warm/yellow for me as well. I checked on two devices, mine (which suffers the red tint at low brightness) and my GF. It did stop my red tinting at low brightness.

Having a few different "calibrated" settings would be nice, starting with the current one and maybe having 2 steps progressively cooler.

If I am understanding you correct, you would like to have a user adjustable setting to calibrate colors, settable at boot; that would be great.

Edit: it didn't do much for my red tint, I had the brightness set at 30% instead of Auto, and the tint happens at less than 15-20%

It would be great if you could make a render effect mode that helped this (if possible) I am thinking a good third of N1 have this tinting at low brightness settings.

Here is a link to a post where I have side by side comparison pics of the tint issue. http://xdaforums.com/showpost.php?p=6869595&postcount=5

If render modes can not fix it, I would settle with the option to set a minimum brightness level that Auto brightness is allowed to use. If I could prevent Auto from going bellow 15%, I could avoid the pink tint without sacrificing the benefits of the Auto setting.
[Nexus One Android Development] j.a:
Just tweeted by Cyanogen:

720p for N1 (better quality than Evo!) is now in CM6 thanks to the help from @charansingh and @enomther
[Nexus One Android Development] daveid:
When the wonk is cured, I believe this entire forum will explode taking all of us with it.
[Nexus One Android Development] fitsnugly:
I emailed the dev about the possibility of a widget.....

EDIT: he said he'll look into it when he gets back from vacation...
[Nexus One Android Development] whiteturboz:
Ugh... Every time I wipe the phone to do a fresh install, I struggle to get the LED notifications to work properly. I can't get the notifications to continuously flash, even though I have both the "Succession" box and "Pulse notification light" box checked. Is anyone else experiencing the same thing?
[Nexus One Android Development] ayo10:
MMS Capture Vidoe

Compose MMS,

Attach, Select 'Capture Video'

Press Record

Camera FCs.

Has been happening since RC1, maybe even sooner in the nightlies, but for sure in RC1, and still happening in RC2. Clean install, wiped ROM before installating.
[Nexus One Android Development] merdely:
I can reproduce this on my G2. Have you submitted a bug?
[Nexus One Android Development] maedox:
Same with ChompSMS, so I guess the app doesn't matter.
[Nexus One Android Development] androidjedi:
Good build#14 no probs so far
[Nexus One Android Development] Bryce2010:
Downloading from a text doesn't work for me nightly 11. Now I can't see the naked pic of Chris Brown my co-worker sent me.
[Nexus One Android Development] fuzzysmallthings:
RC2 ... Wonky as ever ... People can't hear me. I can hear them coming out of my speaker? Would love to stop the whole mess but my screen is totally black and none of the buttons work ... Just have to wait for them to get tired of saying "hello?" and hang up to take back control of my phone ... Wonk.
[Nexus One Android Development] :
I assume you already tried DEWONKIFICATOR and it did not work :)
[Nexus One Android Development] makelegs:
It's pretty amazing, if u think about....all this time and the dewonk app is the only thing that's made this usable on a daily basis. I seriously doubt that I coulda stuck it out, otherwise. Thanks, again, MasterBaron!!!

Here's to hoping that Cyanogen truly has this bug in his cross-hairs! :)
[Nexus One Android Development] :
makelegs,

Your are 100% correct, a life saver for me

This rom on 14 is fast, smooth, and stable--and we got Profiles :)

ZERO Wonks

Appreciate your app immensely :D

On a side note for dual flashers--GB will be incorporated into the N1 starting 1-18

Cyan, and it has been mentioned, will be concentrating on the Phone issue--so 720p video is all we need--I think?

We get a fully functional/stable CM7, I may have to contribute AGAIN :)
[Nexus One Android Development] ayo10:
No, not yet. To be honest, haven't figured out yet how to get the appropriate logs from my phone to attach to the bug report.
[Nexus One Android Development] temasek:
From terminal,

cd sdcard
dmesg > dmesg.log

The log named "dmesg.log" will be created in your sdcard root directory.
[Nexus One Android Development] Autinhyeu:
#15 comming... :)
[Nexus One Android Development] temasek:
U smelling it?
[Nexus One Android Development] :
Based on--?

We have no waterfall--Twitter etc?
[Nexus One Android Development] momomok:
maybe based on the fact that 15 is after 14 :D
[Nexus One Android Development] :
:D :D :D :D
[Nexus One Android Development] :
Hey guys, I just wiped my phone right after erasing all my nandroids.

How awesome am I?

fml =(
[Nexus One Android Development] :
:(

You have bu's on your pc, right????
[Nexus One Android Development] temasek:
Best reply for that post. :p
[Nexus One Android Development] :
lol, I wish.
[Nexus One Android Development] temasek:
Automatic restore should do most of the restore job for u, except for some

MAJOR

settings and non-market apps. :eek:
[Nexus One Android Development] :
I'm afraid imfloflo is going to make us get back on topic ;)
[Nexus One Android Development] temasek:
Talking about off-topic. Which thread doesn't off-topic once a while? I believe ALL THREADs have that.

Well, back to subject.

I am patiently awaiting for profiles for the build-in CPU Settings (if it even coming out). Hopefully it is :D
[Nexus One Android Development] :
How do you get that market installer thing to pop back up after a fresh install?
[Nexus One Android Development] :
Yes they do--we are all kids at heart

That would be nice and eliminate SetCPU
[Nexus One Android Development] temasek:
I feel young again reading that ;)
[Nexus One Android Development] temasek:
Open the market once.
[Nexus One Android Development] fuzzysmallthings:
Actually I haven't. Is it a zip? Just zip it and viola? (I hope I spelled that right as I am not referring to the slightly larger violin). Does it run in the background? Will it work for any version of 2.3.3? Do you have a link? Am I asking too many questions?

Thanks in advance!
[Nexus One Android Development] temasek:
http://xdaforums.com/showthread.php?t=935250

All the answers there
[Nexus One Android Development] :
Edit: Incorporated into MIUI for the N1, sorry
[Nexus One Android Development] fuzzysmallthings:
Thanks for the link. I am trying it now. Although I'm still waiting for someone to call me ... ;)
[Nexus One Android Development] :
Thanks guys. =)
[Nexus One Android Development] makelegs:
If u ever want it to pop back up, again, just use TB to un-freeze it. Worked for me.
[Nexus One Android Development] ayo10:
Did logcat and created a new bug report.
[Nexus One Android Development] zitseng:
I hope profiles can set volume settings! :) I don't just want sound on/off, or change ringtone, or choose vibrate or not. It will be nice to be able to adjust the volume.
[Nexus One Android Development] temasek:
There's already a setting for adjusting volumes.

Settings -> Sound -> Volume (Ringtone, Media, Alarm, Notification)
[Nexus One Android Development] makelegs:
Salivating at the mere thought of profiles for cpu settings.......

<drool>
[Nexus One Android Development] sageandonion:
Had my first ever call wonk yesterday on rc2, same symptoms as every one else. Now moved on to #14, never has a wonk with any of the nightlys from the beginning. Strange eh.
[Nexus One Android Development] temasek:
Nvm

Haiz
[Nexus One Android Development] momomok:
TD network is down again

keep throwing me 502 bad gateway

build 15's coming?
[Nexus One Android Development] negroplasty:
Just a piece of info for the devs... been running build 13 since its release and have experienced NO call "wonk" as others are saying. Did a full wipe (formatted all partitions) before flashing it. Also noteworthy is the fact that I have made at least a dozen or so calls (both incoming and outgoing).
[Nexus One Android Development] XfrostX:
Sooo I just updated to build 13 and on my initial boot it said by SD was damaged.. Did a reboot and it turned out fine. Then I went to rom manager and it said I didn't have root, so I lost root some how haha. My touch screen calibration is really messed up too. Guessing I should full wipe and wait for build 15?
[Nexus One Android Development] temasek:
U use Clockwork recovery 3.xx ?
[Nexus One Android Development] negroplasty:
I experienced this ONCE with #13, it was after initial setup and many many reboots, it happened once and a reboot solved the problem.
[Nexus One Android Development] sir*mez:
I'm going thru this right now. I'm backing everything up on my sdcard before I try to attempt to format it. It says my sdcard is damaged but i can still access my files, silly Sexi Nexi!
[Nexus One Android Development] zitseng:
I mean to have that tied to Profile too? Like, for example, I want a Night Profile that will make Messaging notification quite soft, but Phone ring tone moderate loudness. Then, a Day Profile, where everything is slightly loud.
[Nexus One Android Development] temasek:
Ah Ha! Got your meaning. Count me in ............ thats a nice feature to add on to the "Profiles".

So now we have 2 requests for improvements to "Profiles"

1. Have a widget for Profiles (instead of long press Power button :eek:)

2. Have volume settings in Profiles.

Anyone wanna email the dev of this Profiles? hehe :D
[Nexus One Android Development] XxSilent22xX:
:) 10char
[Nexus One Android Development] lokto7:
Update: updated the radio from 5.08 to 5.12, wonkiness is gone!
[Nexus One Android Development] cyanogen:
Beat me to it :rolleyes:

Yeah, I really hope its fixed this time. Please test!
[Nexus One Android Development] BritSwedeGuy:
Maybe coincidence but I had "damaged SD" after flashing 14 (and a worrying amount of entries in LOST.DIR) - formatted and reflashed, so far, so good.
[Nexus One Android Development] maedox:
I assure you it's not. With the 5.12.00.08 radio that is. I haven't tested the latest fix from Cyanogen yet.
[Nexus One Android Development] qiuness:
so why is 5.12.00.08 not included in the latest CM build?
[Nexus One Android Development] lokto7:
Arghhhhh so sorry it's not >< so what makes the wonkiness going away?
[Nexus One Android Development] temasek:
CM ROM does not include radio. If u want update radio, you have to do it separately.
[Nexus One Android Development] BritSwedeGuy:
Interesting as previous wisdom has always been to go with 5.08, which I thought was odd - what was 5.12 released for then? Maybe a megawipe and 5.12 is worth trying...
[Nexus One Android Development] temasek:
Wonkiness update..........
[Nexus One Android Development] meteora:
is there going to be a #15 that includes the new wonk fix today? or we should wait another 24 hours?

update:

here says that the update to prebuilt kernel and module is MERGED! :)

http://review.cyanogenmod.com/#q,status:merged,n,z
[Nexus One Android Development] cyanogen:
A round of builds was just fired off.
[Nexus One Android Development] temasek:
Great!

Once I flash #15 I get my wife to call me every 10 mins for testing. LOL :D
[Nexus One Android Development] stewartk:
i`ve had this radio since it was released and i`m still wonking
[Nexus One Android Development] negroplasty:
not to mention those of us on the previous radio who have never wonked...
[Nexus One Android Development] imfloflo:
I was on 5.12.0.0.8 radio since the beginning and i had wonk too.

No wonk for #14 right now.
[Nexus One Android Development] stewartk:
all this wonking is driving me up the wall.

fingers crossed 15 fixes it
[Nexus One Android Development] Rusty!:
Korean FRG83 update.
[Nexus One Android Development] unknownrebelx:
Any benefits to flashing it? Like what difference will it make, as it was meant for Korea...I'm kind of a noob at this stuff.

Also, I'm really trying to be patient as the nightly 15 builds are dropping. Cmonnnnn passion!:p
[Nexus One Android Development] temasek:
Some tried 5.12 and its been good to them but not others. So it still depends on your location/carrier, etc.

Why don't u give it a try? U can revert back to your current radio if that is not suitable for u.

I'm using 5.08 Radio.
[Nexus One Android Development] Leonid99:
Well, they stopped dropping, no passion in sight. I guess, it means that the compilation failed for most platforms.
[Nexus One Android Development] samuaz:
what is the best performance settings configuration on cm7parts dithering, vm, lock home, etc? Tnx and greetings
[Nexus One Android Development] eug89:
For those of you that can't wait build 15 to try the new kernel and are too lazy to flash it through fastboot I prepared a flashable zip: https://dl.dropbox.com/s/zibu6qr8sb7g70a/2.6.37.2_NOWONK-signed.zip?dl=1

No wonks so far but I've never been able to reproduce it systematically
[Nexus One Android Development] androidjedi:
Link to the 5.12 radio please
[Nexus One Android Development] stocaprimo:
http://xdaforums.com/showthread.php?t=816917
[Nexus One Android Development] Rusty!:
Here: http://xdaforums.com/showthread.php?t=816917
[Nexus One Android Development] qtwre:
I'd like to chime in to say I had the same problem on 12. All of a sudden I had a message saying SD card was damaged or not formatted. This couldn't be fixed and a PC couldn't read it.

I read a text from my friend this morning saying the same thing just happened to him last night. Not sure the details or which nightly he's on. Coincidence?
[Nexus One Android Development] androidjedi:
Thanks for the radio link
[Nexus One Android Development] Mozelstein:
So, I lied.

Lockscreen stopped working and so did Home button. Also, music won't work over BT as of this morning.

WTF?
[Nexus One Android Development] maedox:
I tested the new fix from Cyanogen and it seems to work. Very limited testing though, so I can't say for sure that it is 100 % fixed.

Signed update.zip with the fix for those who can't wait for the next build:

https://dl.dropbox.com/s/zibu6qr8sb7g70a/2.6.37.2_NOWONK-signed.zip?dl=1
[Nexus One Android Development] :
It's for me exactly the same: "damaged SD" directly after flashing 14 and booting the first time - never happened before. :-(
[Nexus One Android Development] Mitch1816:
I have the same problem.
[Nexus One Android Development] the_canuck:
i got the same. i did a scan disk on the SD card, rebooted and everything was ok.
[Nexus One Android Development] sitinon327:
I got the same "Damaged SD card" message when I flashed #13 over #12. I was going to try the "reformat" option offered on the phone, but instead I simply went to "Menu-->settings-->storage-->Mount SD" and everything was back to normal (I didn't reformat it at all...only mounted it via the phone). I've since flashed RC2 and have only seen the "damaged sd" card message that one time...

Giving RC2 a full-day of use today (just flashed it yesterday evening after Mardi Gras parades). So far #13 had given me the best battery life of all the nightlies I'd tried.
[Nexus One Android Development] t0ph0id:
THis is the issue I had after flashing #13 did you restore anything with a backup program like Titanium?
[Nexus One Android Development] daveid:
I got it too, all I did was shut down and pop my sd card into a different device, verified my files were in tact and put it back in the Nexus, voila. No more problems, no lost files, no big deal, crazy it would happen so widespread though.
[Nexus One Android Development] ByerRA:
Nightly Notifications Problem...

Has anyone had problems with registering for Nightly Builds notifications?

I have a premium license and when I go into Settings -> CyanogenMod settings -> System -> Update notifications and press the "register" button it just sits there trying to connect to the server which it never does.

I'm running #14 and I've completely wiped and reloaded with no luck so I've been manually downloading and installing the nightly roms

Any ideas?
[Nexus One Android Development] momomok:
I experience the same "damaged SD card" error the first time I boot after flashing 13 and 14. Simple unmount and remounting fix the problem.

But I notice that my phone seems to be not properly reading photos on my SD card (built-in gallery takes forever to build thumbnails, QuickPic FC everytime I try to browse photos)

I will try to format my SD card using my PC. Just wondering if it is caused by CWM3... I read some posts mentioning CWM3 may cause some SD card problem...
[Nexus One Android Development] sitinon327:
I haven't noticed any problems with my photos or galleries as of yet, but I also steer clear of CW 3.X. I always flash it back to CW 2.X. The only issue I run into with CW is that sometimes when I try to boot into recovery directly from Rom Manager, it takes me to H-Boot instead. It even did it last night after I flashed RA Recovery. When that happens, I have to fully reboot phone, then boot into recovery again. Nothing I do in H-boot will bring me to any of the recoveries.
[Nexus One Android Development] darock159:
Having the same problem registering for updates ever since I did a nuclear wipe. I have been downloading updates manually as well.
[Nexus One Android Development] Mozelstein:
Used CWM recovery and Titanium.

Everyone says that CWM 3.0 causes issues. I assumed that only pertained to restoring backups but I'm not sure that they didn't possibly mean for everything.

I flashed Amon RA and did a wipe and fresh install of RC2 and gapps. So far so good but it took about 12-15 hours for the issues to show up last time. Haven't decided yet whether I'm going to try to recover apps w/ Titanium or not. I'm leaning towards not because the backup was done just a few hours after a wipe AND only a few hours prior to the issues.

Sucks that CWM 3 is causing issues and that ROM Manager says it won't operate normally without CWM flashed...
[Nexus One Android Development] t0ph0id:
I don't use CWM and got these issues, think it was caused by Titanium.

When I've not restored andy apps or data with TB it's fine.

I've re-installed apps from market as and when I need them, then if I want to restore app data using TB I've been doing a nandroid first just incase.

Long process but it's keeping the phone functional and the bugs at bay.
[Nexus One Android Development] Mozelstein:
Interesting, thanks.

Unfortunate that our backup/recovery processes seem to be causing issues...

Given this, I'm probably not going to restore anything and see how it goes. If something pops up again it's either a bug or I need to wipe EVERYTHING I guess.
[Nexus One Android Development] makelegs:
Sorry guys.....it still wonks.

I tried the flashable .zip and also tried Fits' build with the kernel change merged, this morning. No dice. Looked promising for about 3 minutes.

Dmesg: http://pastebin.com/5CjqnDPt
[Nexus One Android Development] mtw4991:
My buddy has an N1 running CM 6.1, can't he just flash CM7-RC2 with just wiping cache & dalvik or are you guys doing full wipes before installing CM7 GB-2.3.3 rc's or nightlies? Been a while for me since I did it, I don't really remember:o