yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] kfir:
Of course it's normal, but we're used to not wait and get everything with the N1 first.

and that's the first time we come second.....

That still suck :)
[Nexus One Android Development] p7x:
By the way, people that are missing the screen off animation, make sure "Animations" are turned on in "Display" in settings, because the screen off animation appears to be controlled by that.

This looped on mine. The thing that suggests a boot loop rather than just taking ages is the way the logo flashes black every so often as if it's reloading instead of just looping the animation for ages.

I tried wiping again, flashing a copy of CM 6.1.0, then reflashing the zip above, and that didn't work either.

I flashed Chris's original copy and that worked fine again, so it looks like Ardatdat's version is missing something somewhere.

By the way, I can confirm that "NetworkLocation.apk" will cause it to loop shortly after loading to the lock screen. If I add it, it loops, if I remove it, it doesn't.

Er, I've been using clockwork recovery without any problem... please don't tell people "rules" when it's only your own experience. It's misleading.

The Google Apps are very stable. Gmail works fine, as does Calendar, Talk, and the old Market. I've been using Google Books, not to mention all the other stuff like Angry Birds. The new Market seems to die, but who cares?

The trick is not just flashing the entire GApps and expecting it to work. Take some time and be careful and everything works fine - the thing that causes the boot loop is in the first time installer because it's made for Froyo.
[Nexus One Android Development] osugsxr:
test GB out for about a hour or so, flashed directly over cm6.1.1 and itheme. No problems installing, just wipe and flashed. First boot up took probably 3 minutes, just wait and be patient. Didn't try to reinstall/unistall any apps to fix anything. Gmail and a few other apps didnt work, just force closed.

The UI looks pretty solid, fairly smooth and no issues, animations are pretty solid! New phone dialer, dont really care for but the UI on contacts is nice. Overall I like it so far, just going to wait for some themes to come along, and trackball support
[Nexus One Android Development] abvthegod:
i mean it worked and everything, but its just like 2.2 stock. I've flashed to rods miui and never looked back. Even sense is better then regualer android. Dont get me wrong the 2.3 on the nexus s is pretty cool it runs very smooth with no problems. The rom that I just flashed here is laggy, missing alot and in no way is similar to the 2.3 on the nexus s. I guess dl it if you wanna see what its about but the sdk gingerbread from micromod was just as good and you didnt have to do anything to the hboot.
[Nexus One Android Development] AndroidStop:
Mmh will rollback to cm cause too much apps do not work
[Nexus One Android Development] nexus9988:
What did you expect?

So you thought that since 2 days passed with the release of the Nexus S they were just going to hand the N1 a 100% version of 2.2? guys this the first AOSP to-date you can't expect it to have a fully working rom this soon...
[Nexus One Android Development] AndroidStop:
No i knew that this is just for testing and i didn't say anything else ... so whats your problem?
[Nexus One Android Development] MrCDWJR:
not sure if its been asked but does anyone know where in the dump/code/or rom is the screen off animation?
[Nexus One Android Development] wildchild048:
What radio are you guys using with this rom?I am using 4.06.00.12-7 and i think i am going to try the others and see what happends
[Nexus One Android Development] AndroidStop:
No i dont know but its definitely not in framework-res.apk->res->anim folder
[Nexus One Android Development] AndroidStop:
I am using the korean 5.12.x radio...working fine
[Nexus One Android Development] wildchild048:
Thanks I think I am going to try 5,12 because my signal is not so good on 4.06
[Nexus One Android Development] Ardanven:
Well I just flashed but will wait until cyanogen relase

This one is realy slow
[Nexus One Android Development] MrCDWJR:
i kind of figured that. it would be great for someone to find it and make a flashable zip of just that for those who want it.
[Nexus One Android Development] :
I get a boot loop after flashing it through clockworkmod recovery, does it just work for amonra?
[Nexus One Android Development] SBERG117:
So when do the rumors of honeycomb dropping start? lol jk..:D:D:D
[Nexus One Android Development] webarnes:
Yesterday:

http://phandroid.com/2010/12/17/is-honeycomb-being-released-as-android-2-3-this-february/
[Nexus One Android Development] Imperial.mack:
Flash over latest cm rom, no wipe
[Nexus One Android Development] tasty_boy:
hey guys, can someone port it to Desire???

can i flash it in my regular Desire??

i envy all of you!

LOL!!
[Nexus One Android Development] jimbob_me:
Having a look at the desire xdevs forum. All the info you need will be there, wierdly enough.
[Nexus One Android Development] martinl1030:
after flashing gingerbread_passion.ctso.zip my phone also lost ra recovery
[Nexus One Android Development] p7x:
People, please stop posting these!

This is an AOSP ROM and therefore flashes the default Android recovery every time it boots!

You can go to /system/etc/ and empty the install-recovery.sh to stop it happening, but otherwise you can still do everything you need in ADB.

Please stop spamming this thread (filled with people that are doing constructive things with this ROM) with "My recovery has gone!" because if you'd read this far, you'd already know why.
[Nexus One Android Development] :
So far this rom isnt so great. I was happy to have gingerbread running but without gapps or camera most people wont want to keep this rom. Also keep in mind that you need to use fastboot to restore your recovery if your break your su command like i did. Im glad to see that so much is already working. I just wish someone could pull the deodexed apps from the Nexus S roms and get them running on this one. :)

I hope the nexus nightly of CM in Gingerbread, last night cmsrc was pumping tons of gingerbread into the repo.
[Nexus One Android Development] jdmoore81:
any way to get the og=fficial twitter app its not showing in the market and i tried to put it on the gapps folder then flashed but its the only app that does not show up
[Nexus One Android Development] p7x:
I've been investigating that... it looks like it isn't compatible with Gingerbread yet, but I don't know if the twitter team are working on it, and I don't know if there's an easy way to override the APK to make it work either.
[Nexus One Android Development] wdfowty:
Uhm, I've read the whole thread, and there hasn't been any constructive development. There have been edits to the scripts, and work-arounds for the recovery. This rom wasn't even posted as a rom, much less posted by the compiler. Half the people in this thread don't even know who originally posted this on their blog.

BTW, has anyone thought to just delete the recovery files before you put the rom on your sdcard? Just resign it (or not), Problem solved.

I don't want to come off like I'm flaming people, but this thread hasn't seen anything constructive from anyone but MicroMod777 and El Daddy.
[Nexus One Android Development] jdmoore81:
and i cant adb remount since upgrading is there a trick or something i need to do
[Nexus One Android Development] Motlaq:
i'm not trying to spam this thread, but how can i get back recovery?
[Nexus One Android Development] uoY_redruM:
By reading a few pages back..
[Nexus One Android Development] blunden:
I made ChrisSoyars (ctso) AOSP Gingerbread build more like other custom roms. Namely I removed the behaviour to reflash the recovery, removed the hboot assert, integrated busybox, added working SuperUser.apk and su as well as adding the build fingerprint from FRG83D to make sure protected apps work if someone puts Market on it. Made some build.prop tweaks as well.

gingerbread_passion.ctso-fixed-signed.zip

EDIT: Forgot to say I also included Stk.apk (SIM Toolkit) for those of us who need it for certain security and credential features. I noticed it seems to lack some drawables for the notifications pulldown. Might see about adding them back if it's of interest.
[Nexus One Android Development] Clarkster:
Pretty sure someone has already removed the recovery files, and fixed a few things, many, many pages ago, I read the post last night, it had a new zip to flash and everything to fix these issues. So while you read the whole thread, you must have missed some pretty important posts.
[Nexus One Android Development] Motlaq:
already did, but i can't find step1 to begn with !.

i downloaded it and put it on my SD Card but how can i flash it while i don't have a recovery.
[Nexus One Android Development] dictionary:
Way to say Thanks to a dev. I'd rather him NOT take the time to fix those stupid issues, and get an AMAZING build of Gingerbread.

I'm slowly loathing XDA members and their mentality. Blah.
[Nexus One Android Development] p7x:
By going back to page 10 or just searching on Google. Are you trolling or just lazy?
[Nexus One Android Development] Kernel Custard:
I don't understand what has happened with fastboot now. I've had it set up and working fine for quite some time now, but after this rom borked by recovery and put me in a bootloop, I can't get fastboot to do anything. I can't fastboot update anything, signature error. And if I try to fastboot flash system or recovery, it just stays on waiting for device.

Interestingly, passimg.zip also no longer works. When I boot into bootloader, it will load the passimg.zip, and when it finishes... nothing happens. I tried three different ones to make sure it wasn't a bad download. I know there's no way I'm bricked. I can access fastboot, and I'm just in a bootloop. But man, something weird is going on that it doesn't want to cooperate with my computer now.

EDIT: This is weird. After I fastboot flash anything, my Nexus disappears from fastboot devices. I have to reboot to fastboot and it will reappear.

EDIT2: Okay, turns out my fastboot problems were due to Eclipse messing with files that I wanted left the heck alone. After fixing everything on my computer I was able to flash clockwork and go from there. I should have a working phone again soon!
[Nexus One Android Development] blunden:
Uhm, I have nothing against him. He is a great guy and I am immensly thankful that he took the time to set up the CM buildbots as well as all the things he commits to CM. The "didn't take the time to fix" comment was just a general friendly comment referring to a statement I thought I saw before saying he didn't fix everything because he didn't feel it was a good use of his time or something like that. Now I can't find it though. Also, I only slept 2 hours last night and then worked all day so what I post might have some rough edges, though not intentional. :)

What mentality is it that you talk about? Did I try to take credit? No. I didn't remove any single mention of either his nick (ctso) nor his name from anywhere in the ROM (well, except for the build fingerprint but that was for Market compatibility). I don't see how I disrespect him or his work but adding a few things and adjusting it to be more user frindly. Please, enlighten me.

And yes, his time is better spent on CM-stuff which is the reason I posted this file at all. It was originally for personal use.

EDIT: There, I rewrote the sentence I think you might've taken offence to. Happy?
[Nexus One Android Development] paulshields:
Grab an N1 recovery image (Amon Ra for me). Install flash_image (howto here). Flash recovery via adb. Restore your backup and you're back in business :).
[Nexus One Android Development] wdfowty:
This thread is so win :D:D:D
[Nexus One Android Development] ChongoDroid:
I'm slowly loathing silly comments about a guy who is adding something to this rom... what did you add? Thanks to Chris soyars AND everyone working on this.
[Nexus One Android Development] dictionary:
Never said anything about you taking credit. :) I think "didn't want to take the time to fix" comes off as rude. As far as mentality, the one that a vast majority (maybe not you) of the new members have, that everything must be done, and spoon fed to them. That devs have to do absolutely everything in their power to make things just right for the end user, when the devs are doing this because they like to, and for themselves. Imagine a world where NONE of these devs shared their work, lol. Man, I'd be so livid.

It's the mentality I see a bunch of people on here slowly assimilating towards. Or people complaining about devs not doing this or that, when it's easy to do it themselves. Instead of maybe the dev doing 90% of the work, and them doing 10%, they want the dev to do it all.
[Nexus One Android Development] wdfowty:
Lol, he only added things that EVERY other rom on these threads has. It's really not that hard to be a winzip dev, look how far King has come ;)

Not to say it doesn't help, but in reality it takes about 5 minutes of effort, tops.
[Nexus One Android Development] MicroMod777:
Did you remove some drawables because you say you'll see about adding them back?
[Nexus One Android Development] blunden:
Sure, reading it again I see how it might've come off as rude. That was however not my intention. I hope you believe that. :) Looking at my earlier posts should remove any such doubt if you can't take my word for it.

I also dislike the notion some people have that the devs have a responsibility towards the end-user. That most certainly is not the case. They should do whatever they like and if they feel like sharing their work, in whichever form it might be the users should be happy. I would most certainly not consider myself a dev since I mostly commit resources like LatinIME dictionaries, drawables etc. to CM, no actual code yet.

Exactly. Did it remotely from work to save me some time when I flashed it myself. Anyone understanding the basic structure of an update.zip and some general knowledge about the differences between stock roms and custom roms could do it easily. Takes very little time and effort. Just thought I'd post it since some people might find it useful. :)

You mean the Kang. ;)

No, of course not. It seemed to be lacking some of them, ie. they did not render correctly for me at least. I was talking about rebuilding the framework with the missing ones added back. I have yet to take a look if they are actually missing or if it's just that it doesn't want to render them for some reason.
[Nexus One Android Development] MicroMod777:
Ok, I've updated a Gingerbread ROM now with Gapps added, and a few other apps!

http://xdaforums.com/showthread.php?t=872441
[Nexus One Android Development] uoY_redruM:
Can you post some pics in your thread?
[Nexus One Android Development] dr1337:
There are no missing drawables. If you read the logcat properly, you'll see that libEGL_adreno200.so is the one that's causing the weird SurfaceFlinger bug (white screen).

What does this mean you may ask? It means that Google's engineers were so lazy they didn't even bother to work on updating the Adreno drivers that are part of every Snapdragon chip because the Nexus S runs on the Hummingbird chip which instead uses the PowerVR drivers.
[Nexus One Android Development] blunden:
Yes, I saw that it errored out causing the white bug. All the other places it happens it then manage to render it anyway. In the case of the pulldown menu it doesn't. Shouldn't Qualcomm be the ones writing the drivers?
[Nexus One Android Development] erikiksaz:
So cool, finally seeing the screen off animation.

Problem is, I can't get the dialer to work, it doesn't even show. The only time I catch a glimpse of the dialer is when I'm backing out of the screen, I'll get a little hint of dialer screen.
[Nexus One Android Development] wdfowty:
Yes, I do believe so. I'm fairly certain we need to have the OTA for these proprietary drivers. I could be wrong though.

May this thread rest in pieces...
[Nexus One Android Development] dr1337:
Yes, but I also expect Google to support a device that they sold for at least longer than 10 months. Hell, even if the iPhone 3G users were already *****ing when their 2 year old phone wasn't "fully" supported by iOS 4.2.
[Nexus One Android Development] dr1337:
I don't think so. The driver that's causing the bug is actually open source. The OTA won't fix this, and I think that's what's holding back the OTA release so far.

http://xdaforums.com/showthread.php?p=7440689
[Nexus One Android Development] JoelOFH:
Go to the dialer. Move the trackball. Solved.
[Nexus One Android Development] blunden:
Yes, at least the OpenGL part of the driver is not open source which is the one we need from the looks of it. As you say we'll probably have to wait for an OTA.

I think the OpenGL code is a separate module. The rest is indeed open source.
[Nexus One Android Development] wdfowty:
Actually, this doesn't "solve" anything, it's just a work-around.
[Nexus One Android Development] dr1337:
Actually you are right, just had a look at the source here -

http://android.git.kernel.org/?p=de...ff;h=fd7978cde74e92941d604d9d1b8b56e7d387a022
[Nexus One Android Development] ruqqq:
Chill guys. You need to wait for the OTA. Its not exactly Google's fault. It has always been like this. The proprietary drivers are managed by HTC I believe. It was the same issue when we moved from donut to eclair I think with ADP1.
[Nexus One Android Development] dictionary:
I've helped out the Dev community WAY more than you can imagine. Just because not everyones name is out there for the world to see, doesn't mean that they aren't actually doing anything behind the scenes. That, and I assume you meant to say "a guy who is adding NOTHING*** to this ROM" ..

One day XDA members will learn how to speak properly, *sigh*

Blunder, I appreciate you helping the N1 community, but it definitely could have been done/said without the negative undertones.
[Nexus One Android Development] tr.slate:
Off topic- seems like in general theres been a lot of rudeness on xda lately, people getting their heads bit off for asking questions etc. Personally this has always been one of the biggest issues posting here. Cant we all get along?
[Nexus One Android Development] dictionary:
I agree to an extent. I am ALWAYS helping people personally. I think most on here have just gotten fed up answering the questions that are asked a million times. If someone searched, tried, tried, searched, then tried again, and keeps failing, and then posts because they can't get it, I'm down for. People who just come and ask, without even really looking around, and reading up, is when we get annoyed. From back in the iPhone days, then the Blackberry days, then the g1 days .. lol. I've always always ALWAYS been reading and willing to help people who have tried to seriously and sincerely help themselves. I've been there before, so I know. Coddling people won't help them though, because the next time there is an issue, they'll just ask again, instead of actually trying.

I guess I come across as harsh to some, and for that I really do apologize. Really just wish more people would research and try things before asking questions.
[Nexus One Android Development] tr.slate:
Totally agree. Just seems worse than ever lately for some reason.

Anyway back to topic...think im gonna keep this rom for a bit. Really stable for an alpha. Thx all
[Nexus One Android Development] ChongoDroid:
Cool, 5 mins back in my day
[Nexus One Android Development] mikroN1:
Chris Soyars tweeted a new version with camera working. http://twitter.com/#!/ChrisSoyars/status/16592279850459136
[Nexus One Android Development] ~David:
Where does it say that the camera is working?
[Nexus One Android Development] abvthegod:
help please

I downloaded and flashed this rom after I updated the hboot to .17 and of course it earsed my recovery. The problem I have is that I never flashed a recovery from the usb I did it over my ohone with Rom manager. I cant do anything from my phone my fastboot from my computer wont even reconize my phone cuz i cant choose date sync on it. Im so lost i dont even know what to do. I even tried to download rom manager from 4shared and i think i downloaded it but I cant install it cuz i have no notifaication bar on the phone.

update

im pretty sure my bootloader is locked and and i dont know how to unlock it with the gingerbread rom i flashed. I guess i have to use fastboot to push some gapps on to my nexus but im not really sure how to unlock my bootloader with the gingerbread rom that i had flashed.

any help to get my with my recovery so i can get this rom off my phone and i will donate to whoever helps.
[Nexus One Android Development] zomer86:
Any progress on gpu support, notifi bar and those white screen?
[Nexus One Android Development] gaeng4665:
should be fastboot oem unlock
[Nexus One Android Development] abvthegod:
still need help will donate

I dont think so but i still need help on how to get my recovery back.:)
[Nexus One Android Development] gaeng4665:
ok to unlock the bootloader it is absolutely 100% sure:

'fastboot-windows oem unlock' or './fastboot-mac oem unlock' or './fastboot-linux oem unlock'

after that try first amonra's 2.0 with fastboot flash recovery xxxxxx.img

it that does not work, find amonra's 1.7.1 and fastboot.....

people did report it works at least with 1.7.1

good luck
[Nexus One Android Development] abvthegod:
im trying to download and install fastboot now but the files that are supposed to be in android sdk (tools) to put in fastboot are not there.

Windows: from the sdk tools folder, copy "adb.exe", "AdbWinApi.dll" and "ddms.bat" to the fastboot folder

i downloaded and extracted fastboot to a folder but i guess the file ext. that i need from android sdk are not in my tools folder.
[Nexus One Android Development] mikroN1:
I'm telling you camera is working. Camcorder doesn't though.
[Nexus One Android Development] ~David:
AdamG and Cyanogen have gotten graphics working on the Desire.

Not sure what or how they fixed it, but, have a look: http://xdaforums.com/showthread.php?t=879168

Just tried loading it and it's the fastest and smoothest any ROM, stock or Dev, has ever run on my Desire.
[Nexus One Android Development] sonnysekhon:
FYI, your link is to this thread that we're on :).
[Nexus One Android Development] ~David:
rofl, thanks for pointing that out. I accidentally wrote that post IN the Desire Gingerbread thread at first :D

Here's the proper link: http://xdaforums.com/showthread.php?t=879168
[Nexus One Android Development] DMaverick50:
What a let down. Other than a new way to place the cursor it seems like It took them all this time to just change the theme? Nothing is faster or smoother
[Nexus One Android Development] ~David:
Wait until the graphics fix is patched into a N1 ROM, it's actually unbelievably smooth.
[Nexus One Android Development] knightnz:
If the files aren't there, then you need to try reinstalling it, as they WILL be there if installed correctly. The last version of the SDK i downloaded had fastboot already included, and adb and fastboot were both installed to C:\Android\Android-sdk-windows\tools\

You should probably read one of the HOWTO guides rather than using a development thread for the basics.
[Nexus One Android Development] DMaverick50:
awesome, sounds good to me. plus i guess this isnt the n1 official so ill bite my tongue (or my fingers as it were)
[Nexus One Android Development] pendo:
for 2.3 they have a new folder, platform-tools. That's where adb, aapt, ...etc are now :)

<edit>

Also, please note that the aapt that is included with 2.3 does not play nice with apktool. Keep your old version handy.
[Nexus One Android Development] jpanamu:
Can I still try the Gingerbread if I have Hboot- 33.0012?
[Nexus One Android Development] Frankenstooge:
Notice the title of this thread: http://xdaforums.com/showthread.php?t=872441
[Nexus One Android Development] djmisi:
Who rooted your Nexus, bud? I mean, if you would of done it yourself, you would of have to know it... It's all good though... Glad you got it now...
[Nexus One Android Development] wdfowty:
Yes, confirmed. Turn off sig check and let it reboot a few times, it's normal.