yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] SiNJiN76:
Is there a setting that I can back up using titanium backup for the call blacklist?
[Nexus One Android Development] mtw4991:
perhaps CM Settings under filter>system apps? Why not just make a nandroid backup and be done with it? Also, when flashing nightlies, CM saves all settings before installing the new rom and restores upon boot.
[Nexus One Android Development] SiNJiN76:
I wanted to restore the blacklisted items after a full wipe. Not that I have many...but i do get those mysterious calls from 800 numbers with nobody on the other end! :eek::D

CM settings don't back up the list. I'm guessing because it's under Call settings. Well, just found a black list program here on xda...gonna give that a try.
[Nexus One Android Development] lolobabes:
My pleasure, feels good to finally be able to help, ahihihihi

This also happened to me, some apps wouldn't open i rebooted with wipe dalvik cache and all worked ok

tried root call blocking? http://xdaforums.com/showthread.php?t=1082129
[Nexus One Android Development] kopaczus:
#102 is up!

Nothing major though.
[Nexus One Android Development] SiNJiN76:
Thanks....that what I had to do and all its better now. Yup that is the program that I found here...w
[Nexus One Android Development] Mayday_XL:
#102 is ****, only problems. :mad::mad::mad:
[Nexus One Android Development] sir*mez:
?!?!?!?!?

Can you elaborate/be more clear? Cause from what I see, this post, your post is ****!!:D:D

Why??? You may ask...

You fail to explain what the problem is, yet make a vague, rude comment.
[Nexus One Android Development] baseballfanz:
For me #102 is good ****s.:D
[Nexus One Android Development] negroplasty:
What specifically? Everything's working great for me...
[Nexus One Android Development] lashtal:
#102:

1. installed from .zip using Rom Manager -> stuck at X screen after reboot (for the first time ever)

2. market opens and immediately closes (no FC message)

upd: 3. and all my google accounts are gone, wth?
[Nexus One Android Development] momomok:
For 2 and 3, try reflash gapps then re-add your account..
[Nexus One Android Development] lolobabes:
on build 100 my N1 had bootloops, I had to do a full wipe, I am not sure if its because i have had flashed quite a number of builds with no wipe but cache dalvik prior to that. I wonder how many rom updates can you do without data wipe until you need to, Anyone guys? ta
[Nexus One Android Development] noisemonkey:
I think I flashed nearly thirty nightlies before I had to do a wipe due to some weird behaviour
[Nexus One Android Development] Mayday_XL:
Can i write in german ? :)
[Nexus One Android Development] lolobabes:
wow thats a lot! I only had about 5 or 6 if i can remember, ahihihihihi
[Nexus One Android Development] loverhime:
I had noticed an issue on #100, from #98 with wipe cache and dalvik every time.

It told me need to put sd card to use camera and gallery. But all my apps are on a2sd works properly. Reflash #98 and #100 issues still here.

Finally I repartition sd then restored #98 backup works fine now.
[Nexus One Android Development] Dirk:
Ive been using CM7 nightlies since the beginning, flashed almost every nightly and haven't needed to wipe data once :D
[Nexus One Android Development] Mayday_XL:
#103 is on.
[Nexus One Android Development] loverhime:
I noticed gallery and camera issues on #98,100,102.

It says need to put sd card to use these apps.

But my sd is already mounted and other apps on a2sd and media files work properly.

Back to #96 now seems find.

Is it just for me？

Sorry for my english.
[Nexus One Android Development] puttytatko:
the cm7 theme app breaks the notification power widget on change..needs restart to fix...
[Nexus One Android Development] vajda:
Maps

The market wants me to upgrade Maps to version 5.6.

I downloaded gapps from the OP.

Is there any reason not to upgrade? (like gingerbread compatibility..)
[Nexus One Android Development] Rod3:
No, go ahead and upgrade. The latest "official" Gapps are obviously older.
[Nexus One Android Development] momomok:
Search for "Notification Restart" to ease your pain. It is a tiny appear that serves only one purpose - to let you restart the Status Bar on-the-fly
[Nexus One Android Development] vajda:
GPS and apps

So many questions.. Sorry about that.

Basically, I did a fresh reboot and ticked the GPS to start it.

I don't see any GPS icon in the status bar until I start an app that uses it.

For example, google maps.

When I start the maps app, I can see the GPS icon in the notification bar and after about 5-30 seconds I get a lock and everything is working fine.

(I used it for like 5 mins)

When I go to my home screen, the gps lock is lost.

I no longer see the GPS icon.

When I open maps again, the GPS starts blinking again and I get another lock.

It seems the GPS turn itself off whenever the active app doesn't use it.

Is that right? Because I thought it needs to be on always.

I found this out when I tried to "check in" in facebook places but it didn't want to work.

I use the "GPS Test" app to monitor my GPS.

When it got a lock, I moved to the facebook app and the lock was lost.

I could see on the map my current location and tried to add my place (adding a new place) but it said:

"the place could not be added at this time"

Can you confirm this is the same for you?

I thought maybe there is a setting maybe for the GPS to sleep when not needed.

I cleared the cache and data from the facebook app. Didn't help.

Do I even need the GPS to be ON when add a new "place"?

I'm not sure where is the problem.. it can be in facebook.

I do think the GPS shouldn't get disconnected when moving to an app that doesn't use it.
[Nexus One Android Development] Neitmrh15:
Coming from 7.0.3 to Nightly 103 - My app drawer feels laggy.
[Nexus One Android Development] Babydollll:
I generally do a complete wipe every 15 nightlies or so... I've never had any problems but I always attributed that to the full wipe on a regular basis. Your comment makes me think I've done extra work I didn't have too... :( :(

I didn't write that. ;) Prove it!!!
[Nexus One Android Development] FaithCry:
definitely know what you're saying... its felt laggy for a while. only downside to using adw :(
[Nexus One Android Development] momomok:
Your GPS is working fine.

The GPS icon disappear once there is no more foreground app requesting it.

It has been like this since the first day i got my N1 (by that time, it is running vanilla Froyo 2.2.1)

As for the checkin issue. I can't really help, as I don't use the official FB app. (FriendCaster is always my personal favourite :))
[Nexus One Android Development] zybertooth:
Anyone having problems with TBA in 102?

I'v been using the smalli patch ever since, but this time, I got some build errors. When rebooting, the phone won't leave the Nexus X logo. Tried wiping cache & dalvik, but still won't boot. :-(

Looking at the next nightly, I see some LED changes. Hopefully those fixes/changes will remove this problem.
[Nexus One Android Development] Neitmrh15:
I re-installed wildmonks kernel and it feels faster.
[Nexus One Android Development] B1ny:
All Android versions and phones, work and have worked like this since Android came out.
[Nexus One Android Development] SiNJiN76:
104 lost root.
[Nexus One Android Development] gururise:
Same here.. I lost root after installing 104.
[Nexus One Android Development] zybertooth:
Solution for now is to not use Track Ball Alert (Pro)... sticking to in-built CM7 led notifications.

Staying w/ 103, too.. :-)
[Nexus One Android Development] avelec:
+1 Same just updated and also lost root. Is there any special method to root 2.3.4?
[Nexus One Android Development] cpm:
I've replaced ADW with "Gingerbread Launcher Free", which is basically the stock launcher. Downloaded from the Market. Using it several weeks now with no issues. Much prefer it to be honest.
[Nexus One Android Development] lolobabes:
ouch! thats a pain in the butt... am still on 103
[Nexus One Android Development] temasek:
I lost root too flashing my own kang build but for o2x. Was about to flash my own kang build for N1 when I realised I lost root for o2x. Had to abort ......

My first time losing root. :(

Its tougher to recover root in o2x than N1. Whole of /data corrupted too (ext3 partition). Damn :(
[Nexus One Android Development] zyonee:
Root (su) is working on my Nexus S using fresh kang. Currently compiling for Nexus One too. I think I know what happened. Yesterday evening, local time (about 12 hours ago), i did a repo sync. For people not into this, that means I'm synchronizing the latest changes/commits from the official CM7 source repository to my computer before I compile a new kang.

While doing this, I got some kind of error concerning "android_packages_apps_Superuser". I'm guessing that this made the superuser portion of the ROM malfunction. It synced fine this morning, though, and that's probably why my Nexus S kang is working fine. Tested with Root Explorer, mounting /system read-write and then read-only. No problems. So just wait for the next kang and it should be fixed again. ;)
[Nexus One Android Development] Dirk:
So what's causing these root issues with #104? Is it a coincidence that the Chains SU app was updated from the Market in the last day or two?

Anyway, not flashing this one!
[Nexus One Android Development] zyonee:
My guess is that since SU was updated, something went wrong at the point of integrating it in the CM7 repo and it went missing. It turned out that my Nexus One kang had the same issue. Nexus S version works. Weird. Have to nandroid restore my wife's N1 now. :eek:
[Nexus One Android Development] crachel:
http://androidsu.com/superuser/

just install SU from recovery
[Nexus One Android Development] temasek:
Or u can use Super One Click root

http://xdaforums.com/showthread.php?t=803682
[Nexus One Android Development] tbrun:
Thanks crachel - that fixed it.
[Nexus One Android Development] Lost Dog:
Well, I'm kind of stuck.

After the 104 nightly I'm getting a continual reboot at the cyanogen boot screen. Flashing my backup (after a wipe) did nothing. Still a boot loop. I tried flashing 103 and still a boot loop.

I've been one-click rooted so I decided to OEM Unlock the bootloader to get "official". Now that I'm unlocked all the same happens. I tried flashing su from the link above and still no luck.

Help! Any suggestions on how to resolve this?
[Nexus One Android Development] avelec:
Thanks crachel but which one? There are 2 different one (one with bin):

Eclair/Froyo/Gingerbread/Honeycomb (2.1, 2.2, 2.3, 3.0)

1. su-2.3.6.3-efgh-signed.zip mirror (md5: a2844ac335a5c1cfdb9bea2fc041b415)

2. su-2.3.2-efgh-bin-signed.zip mirror (md5: 9a1d14ac8e59d814f0ca2ea03f3477d6) su binary only

Thanks in advance.
[Nexus One Android Development] temasek:
1st one includes su + su's binary

2nd one only su's binary

I would go for 1st unless u just need the bin.

Oh btw, the su issue in nightly was fixed. Next nightly or whoever building kang build will have no su issue thus no more losing root.
[Nexus One Android Development] temasek:
Format /system

Flash cm7 rom

Flash gapps

Reboot

If lose root, use superoneclick root and then update su from market.
[Nexus One Android Development] avelec:
Thanks temasek, I decided to nandroid back to 103 and is all good for now. So I just wait for 105. And actually don't see any drastic improvement with each nightly. My n1 has been running so fluid with no problem. Seems like the CM team has push the n1 up to the max already. Maybe time to update to sensation?!
[Nexus One Android Development] temasek:
I wouldn't go sensation. Specs wise so so. G2X / O2X much better choice or else wait for Nexus 3

Yeah agree on n1. Just checked my n1 and was running for 2d 4hr with 63% left. :)
[Nexus One Android Development] Lost Dog:
That did the trick!! Thank you! The key was formatting /system. I'm back up and restored with a backup.

Looks like this little adventure pushed me over the edge to both install adb on my linux box and OEM unlock!
[Nexus One Android Development] legolas.w:
Anyone know what are new features in the LED settings of the new nightly builds?

Thanks.
[Nexus One Android Development] fitsnugly:
Not for the N1, its P99x specific
[Nexus One Android Development] Mayday_XL:
#105 is on.
[Nexus One Android Development] lebartman:
And su is ok.

:-)
[Nexus One Android Development] jimmytango:
Anyone having auto-rotate issues?
[Nexus One Android Development] sir*mez:
Do you have 0 degrees checked in: settings>cyanogen mod>display... if not check it!!
[Nexus One Android Development] jimmytango:
Wow that was simple. Thanks man.
[Nexus One Android Development] makelegs:
I readily admit to doing a reboot before I thought about checking the 0 degree option...I'm not sure I understand the point of it, myself. But I've only had a single cup of coffee, so far, this morning ;)
[Nexus One Android Development] suikerchiller:
hi there, have to admit I'm all fairly new to this whole rooting thing. Had an all nighter yesterday, unlocked and rooted to the #105. It all works grease lightning compared to the crappy Vodafone retail version I was running :) Have a problem though, but not sure if this has to do with the build of this ROM.

I downloaded a theme this morning: https://market.android.com/details?id=com.cgas.jamtbf.free&feature=more_from_developer

installed it and it's visible in my Theme Chooser. When I select it in chooser it applies correctly. But when I look to my phone the old theme is still active. Rebooting it doesn't seem to change it to the new theme either...

Anybody know what's going on? Just checking if it might has to do with this specific build, if not please forgive me for wasting your time :)
[Nexus One Android Development] shockaholick:
Hey Eveyone,

I never have used any of the nightly builds, and was curious if there is a huge difference between nightly and stable? I'm currently using cm7.0.3 stable. But the two issues I'm having are, one, the gps is intermittent and only works when it wants too. And two, I have tmobile and used the wifi calling feature fine on cm7.0 but it doesnt work with cm7.0.3.

Would love to hear feedback who maybe had the same issues or could answer my questions. Thank you to all who reply, and I do love this ROM! Thank you again!
[Nexus One Android Development] makelegs:
Stick to Rori's themes. I, personally, like cyanbreadx the best.
[Nexus One Android Development] makelegs:
Stick to nightlies...stable and RC is a little misleading. They're all just a massive WIP.

Not sure what current status is on wifi calling, though. I use SIP if and when I need that functionality...which is almost never.
[Nexus One Android Development] CAL7:
I'm on #105 and gmail is not syncing correctly. I get new emails, but if I delete it from my N1, it isn't reflected on the Google servers. Also, my "unread email" count on the phone is wrong. Anybody else?

Or any ideas how to clear? (I cleared cache from Manage-Applications-Gmail, but I can't clear all data without losing the account since it's my primary).
[Nexus One Android Development] :
You won't lose your account

Clear cache and data

Then when you reopen GMail on your homescreen it will reload

I do it all the time
[Nexus One Android Development] CAL7:
Thanks for the quick response. Did it and all is good.
[Nexus One Android Development] baseballfanz:
Clear some room on system and your wifi calling app should work again. I had the same problems till i deleted some system apps
[Nexus One Android Development] FaithCry:
106 is up!
[Nexus One Android Development] lolobabes:
hope no more losing root! ahihihihi
[Nexus One Android Development] temasek:
It was fixed on build 105
[Nexus One Android Development] imfloflo:
Just flash 106, after wipe cache and dalvik cache, having some issue with localisation on gps.

Gps find me in USA with maps but i'm not and find me in the good place with foursquare or gps statut.

Reboot and after wiping maps data all is fine, funny bug
[Nexus One Android Development] krazi3azn:
My titanium still doesn't work :/

Should I try flashing down to a stable release from 106?

Would that cause any problems?
[Nexus One Android Development] temasek:
I assumed u have root rights.

Try uninstall and reinstall titanium app
[Nexus One Android Development] houzuoguo:
Has anyone noticed that LBE privacy guard does not list any app with nightly #105?

Also although the dynamic range compressor is working, but after switch a song, the first beat is incredibally loud :D
[Nexus One Android Development] seamonte:
Look forward to a awesome version 2.3.4:)
[Nexus One Android Development] temasek:
It already is for sometime already.
[Nexus One Android Development] karimaelo:
I've installed 106 by wiping cache and dalvik but the cyanogen icon keeps loading without starting the phone. I tried 105 and the same happened I was on build 102 with no issues. I dont wnt to wipe all data coz i have messages where i want to keep. How can I get my messages back without starting the phone if using ADB thru pc any idea?
[Nexus One Android Development] shmigao:
Did you wipe dalvik / cache before our after flashing? Try before flashing
[Nexus One Android Development] lolobabes:
darn am tired of flashing custom kernel and ss4n1 again and again, when will this nightly builds stop? (not that im complaining just thinking out loud, ahihihihi) :D:D:D
[Nexus One Android Development] lolobabes:
this happened to me too but on an earlier build, i had to revert back to my backup (back up apps thru TB and messages thru backup messages) then fresh install of latest build(data wipe), no other way for me then.... some may have other means:D:D:D
[Nexus One Android Development] vajda:
Lock from clock

Eh, I'm really like my own title.. lol :)

Anyway, I think I've found a bug.

1. Open the stock clock app

2. While being on the main screen app (weather+time screen), press on the power button.

3. The phone will have that tv-effect thingy and becomes black. (sleep)

4. Wake the phone using the power button or via the trackball..

5. The phone is not locked.

NOTES:

- When I don't use a pattern lock, it seems to only work on the main screen.

If I lock the phone using the power button in other other screen, for example the alert screen, I do get the sliding lock screen on waking.

- When I use pattern lock, on wake the phone is not locked but I can't go anywhere because whatever I press, the next screen is the pattern lock.
[Nexus One Android Development] moe.ze.chief:
I've installed #106 and did a Full Wipe and Dalvik Cache Wipe and then I flashed Darktremors A2SD .zip but A2SD doesn't work, any suggestions?
[Nexus One Android Development] te_quiero_forever_girl:
LOL this guy had no idea wat the h3ll he was talking about
[Nexus One Android Development] jens1288:
did you run

a2sd reinstall

in terminal? or use a2sd gui off the market to turn on a2sd
[Nexus One Android Development] baseballfanz:
Did you partition the sd card?

Also did you run the command scripts if this is your first time using dt a2sd
[Nexus One Android Development] mtw4991:
Which DT script did you flash? Ext2, 3 or 4? How much space do you have in /system? What order did you flash rom/kernel/DT? Flash DT before reboot? More info please.
[Nexus One Android Development] temasek:
Wrong thread.

Pls post questions in DT thread.

http://xdaforums.com/showthread.php?t=715940
[Nexus One Android Development] momomok:
Dear temasek,

Is there any big difference between your gapps and the gapps-20110613?
[Nexus One Android Development] moe.ze.chief:
I used A2SD GUI from the Market and i have a EXT3 partition with 1GB.
[Nexus One Android Development] sir*mez:
Do you have enough space in /system?
[Nexus One Android Development] moe.ze.chief:
I did a Full WIPE and only installed the Rom, nothing else, so i think it should be enough space in /system

I flashed it in this order: Rom->Kernel->DT->Gapps
[Nexus One Android Development] temasek:
Not gonna comment much on that but I'm using 0507.

I'm skipping the official 0613 gapps, at least for now.
[Nexus One Android Development] shmigao:
If I am not incorrect, dt should be flashed last
[Nexus One Android Development] Rimher:
MIUI Rom just implemented this new lockscreen:

http://xdaforums.com/showpost.php?p=14904003&postcount=342

and it looks amazing.

Isn't it possible to have something similar in CM?
[Nexus One Android Development] Autinhyeu:
great: http://review.cyanogenmod.com/6267 :D
[Nexus One Android Development] k3vink3vin:
I am able to reproduce this bug :)
[Nexus One Android Development] Devastatin:
The bug happens on stock
[Nexus One Android Development] iron@ss:
Build #107 is up! :D
[Nexus One Android Development] lolobabes:
I agree! This would be awesome! ahihihihi
[Nexus One Android Development] FaithCry:
what does this commit even mean? we can use the camera app?
[Nexus One Android Development] Autinhyeu:
anyone have issue with #107??? i cant connect to wifi network...
[Nexus One Android Development] :
107 is fine for me, no issues

Sent from my Nexus One
[Nexus One Android Development] lolobabes:
fast and furious here
[Nexus One Android Development] vajda:
Thank you.

I guess I'll wait for an RC before submitting this bug.
[Nexus One Android Development] Autinhyeu:
sorry my mistake... :">
[Nexus One Android Development] fitsnugly:
It's for the glacier FFC, even says glacier in the description. Has nothing to do with the N1.
[Nexus One Android Development] Autinhyeu:
On #107, anyone have issue with speaker when calling??? its very low :(
[Nexus One Android Development] shmigao:
Yes this has been on and off over the last few nightlies
[Nexus One Android Development] baseballfanz:
No problems here, if you guys using dt beta that might be where your problem is
[Nexus One Android Development] :
No problems for a long time, nightlies running fantastic . Using s2e, no problems too.

Sent from my Nexus One
[Nexus One Android Development] Marco Schaap:
Hi Xda friends,

In reply to people who are having wifi connect issues with build # 107.

Just 10 minutes ago I've had the same issue, this is how I solved it:

1. Enable WiFi

2. Delete every saved wlan network

3. Disable WiFi and turn on again.

4. WiFi will start scanning networks again, select your network and enter the passphrase, now WiFi should connect...

If not try reboot or clean flash again. Hope this helps!
[Nexus One Android Development] cpm:
#107 just boot loops for me, first nightly to do that too. Skipping.
[Nexus One Android Development] BIG FELLA:
#107 is running really good for me. No problems at all.
[Nexus One Android Development] te_quiero_forever_girl:
anyone experience charging led not working on #107 ?
[Nexus One Android Development] noisemonkey:
Works alright here
[Nexus One Android Development] Autinhyeu:
and no low speaker calling issue??? i have it... :(

BTW: when a new nightly released, i must flash ROM, then flash DT A2SD again, or just flash the ROM???
[Nexus One Android Development] cr0wnest:
My phone is acting up just after i flashed to 107. Had problems with my google account and some apps, so i decided to do a fix permissions via ROM manager then i rebooted and discovered the following.

Home button doesnt work (Although i do feel the haptic feedback), lockscreen is gone (the phone just lights up to the homescreens immediately) and some of my apps magically disappeared and i had to reinstall them. Not the first time my apps vanished, but the home button issue and missing lockscreen is disturbing. I have to use widget locker now in order for me to have a lockscreen.

Also my volume rocker always turns the screen on, i cant seem to disable it even though i unchecked it in the settings.

EDIT: Ok seems some of my other apps (Quickpic, Go SMS Pro) are having FC's when i try to perform certain functions. Only a reinstall seemed to have fixed it. Ive had this sort of problem before after flashing nightlies, but not on this scale.
[Nexus One Android Development] temasek:
Flash dt last after every flash of rom. Once done wipe /cache and u will no longer have low volume issue.
[Nexus One Android Development] Autinhyeu:
thanks! its work :)
[Nexus One Android Development] Arkalos13:
same here. after build 101 worked fine, i tried 106 and got boot loops, and now 107 the same. any idea what the problem could be.