yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] rickytenzer:
Long-press to kill working?
[Nexus One Android Development] simms22:
thats what i thought it would be, i forgot your post about it earlier. as soon as i wrote to restore your nandroid, i remembered :)
[Nexus One Android Development] wonderwout:
Tried it, no problems here. Tried stock and Handsent
[Nexus One Android Development] rori~:
same here,no prob..
[Nexus One Android Development] mtw4991:
hehe, yep me too and thanks for reminding me...210 is up and working. not worrying about contacts and camera...going to 212 in a sec.
[Nexus One Android Development] mtw4991:
so Camera and Contacts are both ok in 212?:)
[Nexus One Android Development] :
Also turning on the flash while recording is bad ass..
[Nexus One Android Development] ieon:
i first saw this browser glitch yesterday.... havent noticed it today yet
[Nexus One Android Development] polo79:
Regardless if you think it is needed for technical reasons or not it still would be a nice feature for a lot of people. A browser exit button is not a task manager where sometimes important apps are killed. We are talking about the browser, sometimes I want to close the thing. Not pretend close it ya know? Also, every 3rd party browser has this feature. I would think there could be a couple technical reasons for this but that is neither here nor there :)
[Nexus One Android Development] brian(::
is rc2 currently the newest or is the latest nightly '7-26' ?
[Nexus One Android Development] The Jones:
Does it cause problems if you don't close it?
[Nexus One Android Development] polo79:
Well I am of the old school thinking that keeping your browser open and running eats up a little extra battery as well as memory. I really dont want to start another big task manager argument (I for one haven't used one in a year) but what does it hurt to have an exit button on the browser? Or how about instead of long press "back" to bookmarks (does anyone use that?) Instead it closes the app.
[Nexus One Android Development] MontAlbert:
wondering this myself- i am assuming it would at least be equal to it seeing as the fembot makes a new build every 12hrs or so when a change is made to the github. so in 12hrs when a new nightly is released that nightly will definitely be newer. as for now- not sure. I would go for the nightly tbh if you want the absolute cutting edge latest.
[Nexus One Android Development] superg81:
ok,i went back and looked again and all i can find is a FC.im not having the typical force close message.no message at all.it just goes back to my home screen.

thanks
[Nexus One Android Development] dlb92:
Speed throttling with CM6 nightlies

So I've narrowed the problem to the CM nightlies. If I install the nightly I have to do a factory reset from inside the settings/privacy menu (the reset from the HBOOT menu does NOT work) and that brings my speeds up to 2-3mbp/s, as soon as I reboot though the speeds drop to below 600kbp/s. I dont install any apps and the backup/sync features are off. If I factory reset again the speeds are back up but as soon as I reboot again the speeds drop.

I have my wifes phone as a control so I know its a problem with the nightly or some settings with the nightly.

What is going on, any suggestions? For now its back to stock frf91..this is REALLY annoying. Has no one else noticed this problem?

T-mobile, Florida HSPA+ network
[Nexus One Android Development] katiepea:
I went back to eclair cm awaiting apps 2 ext and my connection problems disappeared. I couldn't stay connected to H on cm6 but when i went back down I'm nearing 5mb consistently. This is such a huge difference it'll take a lot for me to care about froyo again. I'm still using the froyo radio. -Los Angeles T-Mobile.
[Nexus One Android Development] NguyenHuu:
not to be rude but, the last couple posts of yours is how you dont like froyo and cm6, why do you keep trollin this thread for then? if you decided to go back to eclair then okay, no need to keep posting in here saying how you dont like cm6, it's nightly builds this is expected. it took a long time before eclair final was release and you can enjoy it like you do now. If you beta tested eclair as it was release it was filled with problems as well. it was only "final" recently.
[Nexus One Android Development] xghostyxjokerx:
can soneone tell me what this is im currently using the cm 6.0 rc1 from cyanogen and i see this thread but no detail as to what this is??? is there a page in here i can look at or someone please give me the explanation to this???thanks!!!!:confused:
[Nexus One Android Development] Smokeaire:
Read the first post on page one of this thread. Always good to start at the beginning. :)
[Nexus One Android Development] xghostyxjokerx:
[NIGHTLY] [ROM] [FRF91] CyanogenMod 6 for vendor passion (HTC Nexus One)

--------------------------------------------------------------------------------

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.

What are Nightly build ? : auto compil build from the CyanogenMod github, each time there are new corrections on it. This version change each night, and aren't support officialy, if you find bugs/issues you can/must discuss here.

Warning : Not for new user, flash this build only if you know what you are doing !!!

There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps from his roms, after flashing rom don't forget to flash Google Addon package if you want it.

dont understand is it better than the orignial cm6 or what?
[Nexus One Android Development] notxel21:
When I connect to wifi and my house and use the Speedtest.net app I'm connected to the closest server to my house which is about 60 miles away. But when I'm on 3G the app connects to a server in NYC and I live in Fl. And my DL speeds are horrible compared to when I was on earlier Nightly versions.

Anyone experiencing this and found a fix or cause? Thanks! :cool:
[Nexus One Android Development] Smokeaire:
The nightly builds are to test changes, test possible new features

These are not necessarily better than the release candidate. Nightly builds can contain bugs, so this thread is for us to report bugs that we find in testing these builds, but not to complain about the build. Remember, these are test builds.

If you are using the RC, then the RC thread is where you will post bug reports.

I hope this helps. :)
[Nexus One Android Development] Smokeaire:
Have you turned on GPS before starting speed test? If not then try it, it should find the closest server to you.
[Nexus One Android Development] xghostyxjokerx:
o okay great thanks!
[Nexus One Android Development] notxel21:
I've tried this to no avail. :(

Still connects to NYC even though I'm in FL even with GPS on. :confused:
[Nexus One Android Development] Smokeaire:
I'm in Missouri, when I use Speed Test without gps the closest server is in NJ, with gps it's in OH, sometimes it will pick a server in KS. Go figure.
[Nexus One Android Development] SiNJiN76:
You have to loooooooooooooooooooong press it this time. :eek::D
[Nexus One Android Development] mtw4991:
Getting process.acore fc with folder organizer contacts, but not with drawer contacts. will try to clear contacts data and resync I guess
[Nexus One Android Development] jlevy73:
Camera works but you have to delete and re-sync contacts in 212
[Nexus One Android Development] :
So uh..my signal meter is gone...wtf
[Nexus One Android Development] jlevy73:
What is your VM set at? I use 24 and that seems have got rid of of the process.acore issues.
[Nexus One Android Development] rori~:
..I use 32 and have no process.acore issues..
[Nexus One Android Development] wonderwout:
Known 212 issue:

http://xdaforums.com/showpost.php?p=8670954&postcount=6912

Edit:

http://forum.cyanogenmod.com/topic/...n-of-nightlies/page__view__findpost__p__74359
[Nexus One Android Development] mtw4991:
Delete what? I cleared data in settings>applications>contacts and ticked/unticked sync contacts. Should I delete all contacts and let google re-sync/dl them?

VM heap is set to 24 also. It only happens when clicking on a contact within apps organizer's folder. The folder opens fine but when you click a contact .acore fcs. Probably related to the contacts issue?
[Nexus One Android Development] jesemalave1:
my balls are gone

wtf lol if you read 10 pages before you blue balls bars wouldnt be gone lol

jk im stoned
[Nexus One Android Development] wonderwout:
No: Goto settings/ Applications/Manage applications/ 'Contact storage' and clear data. Then re-sync your data and Call Id should be resolved.
[Nexus One Android Development] rori~:
yeah delete all contact storage and resync...
[Nexus One Android Development] :
They need a copywriter on their team. lol
[Nexus One Android Development] rori~:
ah,exactlly, that´s the right thing..
[Nexus One Android Development] mtw4991:
oh Ok, never messed with storage before, lol....still learning this mod'n thang!

EDIT: Fixed the caller id thing. Changed VM heap from 24 back to 32 and rebooting...see if that helps as I'm still getting FC's with the Folder Organizer Contacts Widget. weird...
[Nexus One Android Development] Festaman:
I just flashed 212 and the bars for my cell service are gone. Is this a feature? Can't find where to turn them back on
[Nexus One Android Development] wonderwout:
This will delete your 'Call log history' entries so back-up or lose it. Also reported that Facebook contacts with non-synced names have to be synced manually again
[Nexus One Android Development] wonderwout:
http://xdaforums.com/showpost.php?p=8670954&postcount=6912

And onwards
[Nexus One Android Development] gadgetgaz:
My message threads are still be deleted from the top of the list. I did a full wipe, restored my messages using Sprite backup and it still happens. Then I flashed back to 210 and it's till doing it! I wiped cache and dalvik cache each time.

Could anyone please help with suggestions? Thanks.
[Nexus One Android Development] wonderwout:
I'm on 212 and I cannot reproduce your issue. I've entered multiple SMS threads, backed out and in and noting gets deleted.
[Nexus One Android Development] jocaferlo:
I have too FC with Folder Organizer Contacts Widget but only if I set that widget to "scrollable" in the widget options. If I uncheck that option (scrollable) the widget works fine.

I am using now build 210. I don't know if this problem is related to the ROM or to the app. There was an update of the app today, I'm using version 3.0. I think before I didn't have problems with this widget. I sent an email to developer saying the problem.
[Nexus One Android Development] makelegs:
Rom Manager...

I noticed that my Rom Manager list of nightlies has stopped at #204. No updates since then. Anyone else have this issue, too??

Edit: Lo and behold..... it seems to have finally updated, again. Weird...
[Nexus One Android Development] simms22:
i dont use rom manager. i use this http://mirror.teamdouche.net/?device=passion&type=nightly :p
[Nexus One Android Development] makelegs:
Not trying to re-hash...but....

Does the most recent gapps bundle include the newest carhome version? Really don't wanna go thru the pain of getting that to work again, but would like to have it in system memory just the same.
[Nexus One Android Development] makelegs:
Ya....that's what I've been doing since 204. Just hate when things are "broken" ;)
[Nexus One Android Development] jesemalave1:
hhhhhhhhhhhhhhhh
[Nexus One Android Development] belair56:
Yes, it has new car home

http://mirror.teamdouche.net/get/various/gapps-hdpi-20101008-signed.zip
[Nexus One Android Development] makelegs:
Pretty sure his point was that it's available FIRST via TD.
[Nexus One Android Development] shotta35:
And they're off...

c'mon buildbot - i got $20 on you tonight. Come to papa!

EDIT -

http://mirror.teamdouche.net/get/passion/cm_passion_full-213.zip

And there goes 213!
[Nexus One Android Development] makelegs:
Thanks for the confirmation... now enjoying an extra 10MB of free memory!!!
[Nexus One Android Development] aiewolf:
Came thru for you tonight.

Downloading 213 now
[Nexus One Android Development] jesemalave1:
true i thought i deleted that lol sorry i dont want to criticize
[Nexus One Android Development] shmigao:
Since nightlies in the high 190s and beyond haptic feedback has been leaving me ever so often. Mostly it just disappears after a while (e.g. while typing) but returns after screen off sometimes only reboot fixes, sometimes even reboot no help and need complete shut down and restart. Weird
[Nexus One Android Development] shotta35:
Seems as if the Signal bars bug is still there. Oddly enough i just wiped and just installed and the bars were there then they disappeared! I went into the DBM thing and enabled DBM and checked bars to hide (still opposite).

Doesn't seem like i can turn off the Galaxy S style thing too in the Notification area. It's unchecked but every reboot it comes back (along with the problem above! - to fix that seems like you gotta uncheck the options (dBM) and then reboot then check it again for it to show the status bars.)

In the reboot/power off dialog box - the text has a upper cell alignment as if some text is supposed to be below it like the Airplane Mode stuff. Don't think it needs any description for "reboot" and "power off" but as of now they look out of alignment
[Nexus One Android Development] makelegs:
No worries...:)
[Nexus One Android Development] SiNJiN76:
Hmmmm. 213 deleted all my ADW catalog/groups.
[Nexus One Android Development] dictionary:
cyanogen: (via twitter)

We are aiming for CM 6.1-RC1 on Tuesday.

GOOD NEWS!!
[Nexus One Android Development] leoccc:
about hibernate mode?
[Nexus One Android Development] SiNJiN76:
Does it really matter since we do nightlies anyway?
[Nexus One Android Development] applejosh:
After seeing the changelog cyanogen just posted, ADW was updated to 1.2. And its changelog says that they have to be recreated.
[Nexus One Android Development] SiNJiN76:
Thanks. I was just about to search for that. But the new catalog navigation buttons make up for the deletion. please wait 2 seconds for an uncompressed image, or press Ctrl+F5 for original quality page
[Nexus One Android Development] goTouch:
213 is great. Very stable!!
[Nexus One Android Development] ~~Tito~~:
How do you guys flash over a nightly? I try and I just get bootloops, I wipe cache and davlik cache, then I flash the newer version (tried this with previous versions too, same deal), then I boot, and I just get bootloops, what gives?
[Nexus One Android Development] jlevy73:
214 is up.

http://mirror.teamdouche.net/get/passion/cm_passion_full-214.zip
[Nexus One Android Development] GuerillaZhou:
what rom are you coming from? if its not cyanogen, you have to wipe everything then flash the nightly
[Nexus One Android Development] niubia:
ha ha ha

cm_passion_full-214 already
[Nexus One Android Development] jlevy73:
Here's what I do, probably a bit of overkill but this is my routine.

1. wipe cache

2. wipe dalvik

3. flash nightly

4. flash gapps

5. reboot

If that doesn't work may have to wipe data as well
[Nexus One Android Development] Autinhyeu:
Flashing 214 now :)
[Nexus One Android Development] ~~Tito~~:
I do that, I dont wanna wipe data cause settings would be lost.
[Nexus One Android Development] andyandrwew:
214!! cant wait till 6.1 this Tuesday (info via CyanogenMOD Twitter)
[Nexus One Android Development] applejosh:
214 fixes the signal bars. About all I've looked at so far.
[Nexus One Android Development] knightnz:
If you're coming from a non-CM ROM then you're probably going to need to anyway as there will likely be incompatible settings for things that will crash the ROM otherwise.

Just restore a nandroid, back everything up with TitaniumBackup, then wipe data, cache, dalvik & battery-stats, flash CM, then restore your apps etc.
[Nexus One Android Development] chrisvuong:
My god, just flashed 213 and restore, setup everything, now 214 already here, how can i follow this? :(..i must flash and do everything again???lost time
[Nexus One Android Development] G1-evolve:
So no 6.1 today no more right?
[Nexus One Android Development] ~~Tito~~:
I am using a nightly, I have been around the block to know that you cant flash over a different ROM and expect it to boot lol, but what do you think could cause boot loops on this problem? It happens everytime I try to, I have tried from 200 - 201 and it boot looped so I restored my nandroid, then I try it from 204 to the latest one and it didnt work, could it be the amount of things added and changes to cause the boot loop
[Nexus One Android Development] triciopa:
Haha we "do" nightlies as in we "do" crack or heroine... this is an addiction
[Nexus One Android Development] NguyenHuu:
what you talking about, you dont need to do anything over. just wipe cache and dalvik cache, then flash new one on top. everything will be saved and kept the same. you do not need to do full factory data wipe!
[Nexus One Android Development] mtw4991:
I dont know but i was using dt a2sd and i forgot to reflash after flashing the nightly and git major bootloops until i reflashed rom +dt then everything installed as it should
[Nexus One Android Development] chrisvuong:
Thế à? cảm ơn đồng chí :x
[Nexus One Android Development] ogdobber:
running 214, On the notification pulldown power widget when I adjust the screen brightness it disappears from the drop down...can anyone else confirm?everything else works good...

-did the same on 210, 211, etc...
[Nexus One Android Development] teihoata:
Yes, this happens on my phone as well
[Nexus One Android Development] shmigao:
O

Check whether it has a tick mark under CM settings / user interface. If it has it should stick
[Nexus One Android Development] jlevy73:
214 still has the contacts bug. Have to delete contacts and re-sync.
[Nexus One Android Development] mik101:
It's doing the same thing to me (disappearing notifications pulldown -- currently on 213). I'm flashing to 214 now.
[Nexus One Android Development] ogdobber:
huh. it was ticked...i unticked it and re-ticked it now it sticks:confused: thanks

one more thing to note, my trackball notifications weren't working, there is a new "manage categories" that I had to select or create for each app....
[Nexus One Android Development] jlevy73:
That manage categories has been there the last couple of nightlies. However, it didn't alter any of my settings.
[Nexus One Android Development] jlevy73:
I know brotha, just saying as a worse case scenario.
[Nexus One Android Development] ogdobber:
i missed that one, I was on 203 for a while....
[Nexus One Android Development] shmigao:
yes i noticed the trackball notifications issue too.
[Nexus One Android Development] ogdobber:
214 contacts working for me (showing up in call)
[Nexus One Android Development] jlevy73:
Hmm interesting. As soon as I went to the call log, all the names disappeared. Oh well, easy enough to fix.
[Nexus One Android Development] rich1984:
was having same issue. thanks.
[Nexus One Android Development] xguntherc:
So how is everyones nightly build running.. Any issues still that everyone has?

I've been on a custom cm build version since 202 and everything worked fine then..
[Nexus One Android Development] jlevy73:
Everything is good. Only bug was the contact one but it appears I'm the only one with that issue.
[Nexus One Android Development] xguntherc:
oops.. My phone did a double post..
[Nexus One Android Development] SiNJiN76:
Manage Categories for LED is FCing for me. Was fine...then I created a category then deleted it because it somehow wasn't displaying the title correctly. Now when I try to go back in, FC.

Was hoping that flashing 214 would fix it...but it didn't. Guess I'll try wiping cache.

Actually...wiping data under cyanogen settings fixed FC issue.
[Nexus One Android Development] cyanogen:
Committed some fixes from Pedlar for this. I'll force a build.
[Nexus One Android Development] cyanogen:
This should also be fixed in the next build.
[Nexus One Android Development] G1-evolve:
The great Cyanogen has spoken!!!
[Nexus One Android Development] apratomo:
215 is up, will that 215 fix all issues above with contacs, trackball notif, camera?
[Nexus One Android Development] Autinhyeu:
OMG @-) build 215 online now http://mirror.teamdouche.net/get/passion/cm_passion_full-215.zip
[Nexus One Android Development] cyanogen:
What camera issue?
[Nexus One Android Development] leoccc:
flash 212 .... flash 213 ... flash 214 .... flash 215 ....looplooploop:rolleyes:
[Nexus One Android Development] DOHCtor:
Gonna flash 215. This build is special because it was forced by Cyanogen!
[Nexus One Android Development] :
The camera.apk was not showing up in the drawer, despite the fact that it was located in /system/app/.
[Nexus One Android Development] DOHCtor:
A few build back, the camera app wasn't showing in the app drawer but there was a Camera.apk in /system/app. But this was fixed since 212, I think.
[Nexus One Android Development] G1-evolve:
indeed, it should. :cool:
[Nexus One Android Development] Autinhyeu:
Anyone have issue with Camera same me? I run Camera app, after i press trackball to take a picture, but it dont work, i must move trackball, then press trackball, its work :|
[Nexus One Android Development] mikroN1:
LOL. Flashing the next one isn't going to stop your bootloop. You need to wipe data/cache/dalvik and reflash newest nightly + gapps.
[Nexus One Android Development] cyanogen:
Oh ya that's been fixed.. Was an error in the manifest.

I'll look into that but file a bug if its not fixed in RC1 when its out.
[Nexus One Android Development] rori~:
ADW has un update :)nice...

It´s all smooth..
[Nexus One Android Development] g4rb4g3:
I tried it too right now and I have the bug too.

Seems like the Camera button isn't selected, when you move the ball it will be selected. Then it works.
[Nexus One Android Development] diz127:
Home button doesnt do anything in 215 I've checked settings in ADW and Cyanogenmod settings :\
[Nexus One Android Development] diz127:
Search button doesn't do anything either.
[Nexus One Android Development] rori~:
Home button works as usual.

Search button works as usual too

No probs at all..
[Nexus One Android Development] ray_f:
Mine is working fine, maybe try do clear the cache?!

Or cleanup the data in ADW...
[Nexus One Android Development] diz127:
Nothing :\ ...guess I'll go to an older nightly
[Nexus One Android Development] DOHCtor:
Why would you do that when it's clearly working for other people, including myself.
[Nexus One Android Development] diz127:
Because its not working for me obviously. If I move to a different nightly I'll be able to see if my phone is the problem.
[Nexus One Android Development] rori~:
I just wanted to say that...:D
[Nexus One Android Development] ray_f:
You reckon it's an hardware issue?!

Maybe try the key test in ClockworkMOD....
[Nexus One Android Development] t0ph0id:
No, just re-delete cache & flash again.
[Nexus One Android Development] diz127:
Restored to 212 and its working fine now. Last time I checked some nightlies effect certain phones and not others. For instance a couple nightlies ago people were missing their camera while mine was working perfectly.
[Nexus One Android Development] diz127:
Tried that too

Not a big deal for me...thanks for the help everyone.
[Nexus One Android Development] xguntherc:
why are so many people having issues with the 205+ nightly's.

I've ran issue free for the last like at least 2 months of flashing every nightly. never had an issue. (other than the night I accidentally flashed a FRF83 zip. lol.

I think I'll try 215
[Nexus One Android Development] diz127:
Yea same here...I have no clue what happened. Never had a problem before.
[Nexus One Android Development] xguntherc:
Thanks for stopping by our little (small, not very many pages) Nightly thread. We discuss and ramble about all things CM.

I'm glad you guys decided to do the Nightly thing. It really has been nice. I enjoy flashing something nightly actually.

You guys that have flashed 212-215. does it have the up and coming CM6.1 app2SD implemented? or no?