yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] dacrannis:
Finally figured it out. Finally got adb method working and reverted back to stock with PASSIMG. I think i am a little out of my league on this one. I will stick with froyo until a more stable and easier to install rom comes out for gingerbread.

thanks all for your help and keep up the great work. We appreciate all your hard work.
[Nexus One Android Development] taief:
i'm in the same situation bro would u plz show me how u fixed it?
[Nexus One Android Development] dr1337:
Hang tight. I'll do a video tutorial to fix your phone.

*Edit*

Video now available -

http://www.youtube.com/watch?v=cAWBFYg4icU
[Nexus One Android Development] MicroMod777:
Well tried to get Gingerbread rooted with busybox but it wouldn't boot. Was using XDA's Kitchen in Ubuntu. Think I'll wait till better build comes with working camera to try again. :)
[Nexus One Android Development] ardatdat:
OK, just modified the ROM to include google apps and superuser

- Nexus One only

- No limitation on hboot version

- Will not touch your recovery, works with RA 1.7 and others

- Google apps included (market), with no facebook / youtube / etc... (you can download and install from market)

- su with superuser.apk included

- Enhanced apn list

- Enhanced hosts file to block advertisement

- Tested OK with 3G / wifi / wifi tethering / bluetooth

- Stock kernel. But you can flash your favorite custom kernel

- Try installing setcpu and work OK! Can overclock using custom kernel

- Camera does not work up to this moment

- Some screen still shows up 'white', just move around with your trackball and should temp solve the problem

Here it is:

GingerBread_ROM_121810_153354.zip

http://www.mediafire.com/?yp558iu8y4k6jut
[Nexus One Android Development] Halocog:
Edit: I need some help - When I try to boot into recovery, I get the android logo with a "!" in a triangle. Anyone know how to fix this? This older rom doesn't have superuser.

Any help is GREATLY appreciated. Thanks!
[Nexus One Android Development] MSigler:
I guess I'll give it a go.
[Nexus One Android Development] MicroMod777:
Sweet! Nice work! :)
[Nexus One Android Development] vanessa13006:
Seems to work fine. Thanks alot
[Nexus One Android Development] djmasque:
If you were to flash a 720p kernel, and add a camera app, would that help? Or is it drivers that are needed?
[Nexus One Android Development] ardatdat:
OK, need to go out for a few hours...

Hope that when come back, some one will find out how to handle the slow performance in home screen.... and get the camera working

Cheers! :D
[Nexus One Android Development] MSigler:
Mine appears to just be boot looping. Keeps flashing the "Android" screen over and over.
[Nexus One Android Development] ha85:
Same here.
[Nexus One Android Development] JoelOFH:
I have the same boot-loop problem. :(
[Nexus One Android Development] ducatman:
idem for me
[Nexus One Android Development] imarcink:
I rebooted in to recovery (adb reboot recovery), flashed a Nandroid backup from CM6.1.1 and re-flashed the GingerBread_ROM_121810_153354.zip provided above.

Someone suggested several pages ago that it was a problem with some incompatible GApps apks that was causing the boot loop.
[Nexus One Android Development] MSigler:
That's the one I attempted to flash from the lastest CM nightly.

Wiped data and dalvik cache first. Flashed. Looped. Pulled battery, tried again, looped. Restoring now, I'll try again.
[Nexus One Android Development] MSigler:
That logcat was set to only report Error and higher btw, adb logcat *:E
[Nexus One Android Development] Halocog:
A word of warning to anyone who installs the Gingerbread roms before this one - It broke my Clockwork Mod recovery. You will have to install amon ra's recovery.

Anyway, thanks for this rom! Google Apps seems to be very unstable on Gingerbread so far. This version seems to work best atm. The new ones worked for me one time and quit.
[Nexus One Android Development] saygun:
boot loop for me with GingerBread_ROM_121810_153354.zip
[Nexus One Android Development] nok07635:
I got bootloop too!
[Nexus One Android Development] macsim:
If you have bootloop try to install it OVER an existing 2.2 without wiping first

Worked for me
[Nexus One Android Development] darkraiderfan:
doing this earased my recovery and now i cant get it back. please help
[Nexus One Android Development] JoelOFH:
Confirmed. Thanks!
[Nexus One Android Development] crowcken:
Erase your recovery???

I don't understand how it has been possible,

because you has flashed a ROM, not a recovery,,,,

???
[Nexus One Android Development] Androith:
Tested by curiosity. Camera does not work, my applications, many not working well, and has a small delay in the ejecucionm and the performance was not expected. Very clean interface. I returned to cyanogen 6.1.1.

2.3.1 cyanogen waiting!
[Nexus One Android Development] seraphimserapis:
If gmail would work it would be perfect for me ;)
[Nexus One Android Development] dr1337:
It actually does. I have it working.
[Nexus One Android Development] WickedStyx:
There's a script /system/etc/install-recovery.sh that overwrites the recovery with the stock recovery.

You need to redo from fastboot

http://xdaforums.com/showthread.php?t=611829
[Nexus One Android Development] WickedStyx:
Same here. Even works after updating gmail via market.
[Nexus One Android Development] crowcken:
Full Android on Passion

Android version 2.3.1

baseband 32.50.00.32H_5.12.00.08

kernel 2.6.35.7-59410-gba07db7 android-buil@apa26 #1

Compilation full_passion-userdebug 2.3.1 GINGERBREAD eng.ctso.20101217.191648 test-keys

WORKING OK, TESTING IN PROGRESS... ;-)
[Nexus One Android Development] negroplasty:
Boot loops like crazy. Tried flashing over a previous froyo installation, as well as after wiping first. Boot loops all day.

HBoot 0.33.0012 .
[Nexus One Android Development] crowcken:
First flash, with full wipe, has boot loop

Sencond flash, over CM6.1.1 and apps installed, works but i need to erase apps

Third, I erase all phone data, but not from recovery, from the settings/privacity/reset

It seems now, with app/data space free, works fine...

Now I'am able to test hard.

Waiting for CM 3.2.1 too ;-) Thank's master!
[Nexus One Android Development] crowcken:
Be patient with your first boot, it takes over 5 minutes...

The difference between the boot loop it's that when flash boot animation

works in boot loop, it seems to dissappear for a few miliseconds, and

in a a correct boot this doesn't happen :p
[Nexus One Android Development] negroplasty:
Ok, so I got it to work by playing around for a minute, not sure what did it though. I flashed the ROM over FRG83D without wipe, boot looped forever. I then booted back into recovery and wiped userdata and did a reboot and got into some sort of safe mode (said "safe mode" on the bottom left of the screen). I powered the phone off and when I started it back up again everything worked... beats me. :confused:
[Nexus One Android Development] AndroidStop:
OK will try to flash this now... hopefully recovery won't be dead :D

using RA's 2.0
[Nexus One Android Development] AndroidStop:
YEAHAAAHH Gingerbread running on my N1... and it runs fine :D
[Nexus One Android Development] AndroidStop:
try to flash this rom without doing a wipe....

I had CM6 nightly installed
[Nexus One Android Development] MSigler:
Yeah, it worked after I flashed over CM nightly without wipe.
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
I just did the conditioning thing for my battery.

Charged fully, then wiped battery stats, now i have to drain it.

How can i drain it FAST?

i have gps on, bluetooth on wifi on

watching a HQ youtube video while listening to music

why is it that when i dont want my battery to drain it drains fast as hell, but when i want it to drain it feels like an hour from 100 to 99?

how can i make this even faster??
[Vibrant Q&A, Help & Troubleshooting] willsnews:
Do a lot of rebooting always kills mine
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
holy ****, its working every reboot gets like 1% haha

97 more reboots to go :(
[Vibrant Q&A, Help & Troubleshooting] Sdobron:
Turn gps on, go outside and actually use it with maps or navigation. Will kill your phone in 1 to 2 hours.
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
rather not its like 30 degrees outside here in Texas ha

so far, 31 minutes used and went from 100 to 76 an hour or two more, and BAM it'll be good.

I put a live wallpaper on and now its running like hell hahah
[Vibrant Q&A, Help & Troubleshooting] Sdobron:
Even if you're indoors maps and searching for signal might help knock it down more.
[Vibrant Q&A, Help & Troubleshooting] T313C0mun1s7:
STOP

Deep cycling is really bad for Lithium-ion batteries. I don't know why people keep perpetuating this myth that you should do this after burning a ROM. I blame Team Whiskey et all, etc . . . blah blah (You flashed our ROM now recalibrate your battery)

Lithium-ion batteries do not have a memory, you do not need to deep cycle them like Ni-Cad, doing so seriously shortens the lifespan of the battery. So unless you notice that the readout for the % of battery charge seems very off from reality don't recalibrate. Even if it is off a little, it will fix itself over time as you charge and use your phone. You don't even need to let it drain a lot. Just use it like normal and charge it when ever you get a chance.
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
A lot of people r telling me it helped them
[Vibrant Q&A, Help & Troubleshooting] T313C0mun1s7:
Um, just Google search Lithium-ion. Read a little about the battery technology for yourself and you will see why it is very BAD advise to deep cycle your battery. After a little more than a year with Li-Ion the battery will only hold about 70% of the charge it held when it was new. Keep deep cycling and you will shorten that time to about 4-5 months. Then these same people come back here and ***** about how crappy their battery was because it only lasted a few months and they will offer as proof that it was always crappy because they had to recalibrate it a frequently. I alway think the same thing to myself when I here this from people, "dumb ass, you killed it."

Hell, the sales rep at T-mobile tried to tell me this crap when I purchased my phone. I asked her where she got her electrical engineering degree with focus on battery technology from. After the puzzled look settled from her face I told her that the advice she gave was about the worst thing you could do to the battery. She didn't believe me, but I told her to look it up on her fancy Google powered smart phone. After she did that she apologized.
[Vibrant Q&A, Help & Troubleshooting] bobbbb:
A lot of people say things they don't understand, don't drain your battery as such, it's not good.
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
I wont do it... but

I've already pressed wipe battery stats does rat mean it already happened or something? Is there anything I can do to reverse this iif I did it wrone
[Vibrant Q&A, Help & Troubleshooting] gagb1967:
Wipe battery stats, does not affect the battery, only deletes the stats saved by the OS. It won't make your battery run faster, or better. These are only STATS saved by the system to tell you where your power is going.

Don't go all psycho about the battery issue. get a cheap chinese knokoff battery from ebay with charger (as I did) and just go out with 2 batteries, even with heavy use, 2 batteries should last you all day. (well, with certain roms, Almost all day)

:(
[Vibrant Q&A, Help & Troubleshooting] T313C0mun1s7:
I am running Axura 2.1 with no changes to the modem or theme and a stock battery. My phone is only about 2 months old but running stock I got about 11-13 hours and now I get 24+ hours when I let it. Normally I just charge it every night anyhow because it does not hurt anything, in fact it is better for the battery.
[Vibrant Q&A, Help & Troubleshooting] dattaway:
Nothing uses more power than the touch screen. Keep scrolling pages and your phone will be a hand warmer.

I've noticed deep cycling lithium ion batteries can destroy capacity to almost nothing quickly. Keep a charge on it whenever you can. The internal resistance is so low, you won't ever notice a "memory." Until the chemistry inside has rotted itself out.
[Vibrant Q&A, Help & Troubleshooting] T313C0mun1s7:
Excellent job of putting into layman's terms the endless cycle of the relationship of heat creating the substance on the electrode that increases resistance, which creates more heat in an endless cycle that is the death of batteries.

In lead acid batteries (like your car, motorcycle, or uninterruptible power supply) oxidation on the plates create this internal resistance and it is why car batteries are rated by number of months, like a 72 month battery. It happens to some extent to all rechargeable battery technologies, but in the case of Li-Ion batteries the internal chemistry actually tear them selfs up over time.

Long story short is the two really big enemies of Li-Ion batteries is deep cycling and heat. In fact if they are not vented well, and allow heat to build up, you get the battery fires you may have heard about with the Dell and Apple laptops that used the Sony batteries. There have also been a few phones that have been known for melting down.
[Vibrant Q&A, Help & Troubleshooting] Saiboogu:
Y'know, I would love to see a big sticky in one of these forums about this. Another voice of reason -- Don't deep cycle your battery, don't cycle it unnecessarily and don't worry about calibration. Your phone calibrates itself all the time and the less often your battery spends any time at low charge the longer it'll last.
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
Thanks guys good thing I didn't go too far before one of you told me not to do this.

Thanks again
[EVO 4G Q&A, Help & Troubleshooting] crimeslunk:
Ok so here is what lead up to the problem. I've been running Vaelpak for a couple of months now flashing updates on it no problem and flashed updated radio ect... no problem. Today I DLed the new Flashable Radio from Caulkin. Did a nandriod backup(I know always to do this). Used the quick boot option in Vaelpak to get to my recovery then flashed the radio. After it was flashed I used the reboot option in Amon RA to restart phone and it went to white HTC evo screen, I waited a half hour and still nothing.

Since this I've tried restoring my previous nandriod back up I get an ABD Shell error saying the restore cannot be done. Tried previous back ups same problem. Oh well I thought I'll just start back over from Vaelpak 2.3 Flashed it and then restarted phone. White HTC screen for 1 hour, no go. Flashed Vaelpak 2.1, white screen, no go. I've been doing multiple system wipes, cache wipes, and Dalvik wipes in between all my flashing and attempts to restore previous back ups.

Today I've just purchased a Micro SD to usb adapter, and a new cable to USB(lost previous one) in order to try to fix this problem myself with you guys' help. Any ideas would be appreciated and I'm not afraid to try some shell commands. Please tell me I'm not bricked this would be a very inopportune time for this to happen.

Supersonic EV2-3 ENG S-OFF

HBOOT-0.76.2000 (PC3610000)

Touch Panel-Atmel224_16ab

Radio-2.15.00.11.19

Recovery RA-evo-v1.8.0
[EVO 4G Q&A, Help & Troubleshooting] fachadick:
Try flashing an older radio.

Sent from my blah blah blah blah
[EVO 4G Q&A, Help & Troubleshooting] Biofall:
The restoration error might be originating from the lack of battery life in your phone, try to charge for awhile, then restore.
[EVO 4G Q&A, Help & Troubleshooting] crimeslunk:
Well the restoring error was due to the lack of batter thank you Biofall

And I still don't see it was possible for a radio to make all my restores and reinstalls of my rom invalide but that was it.

I tried flashing the last known working combo for my phone and it didn't take but after I tried flashing the previous radio on its own and now I'm back in business. So thank you fachadick I think this is 2nd time you've help me out of a situation like this.

Thanks once again glad to see I didn't waste 35 dollars today on a cable and Micro SD reader.
[EVO 4G Q&A, Help & Troubleshooting] fachadick:
The newest radio has issues with certain older kernels. Since nand backups don't backup or restore radios (except for wimax), when you restored your old backup, it was still trying to run the newest radio on the incompatible kernel. Glad it worked for you - with some hunting, you can find a kernel that will work with the new radio. I think netarchys is good.
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
i flashed the stock rooted RUU and i get 100% awake time... anyone else? i haven't tried any other 3.70.651.1 roms..
[EVO 4G Q&A, Help & Troubleshooting] notasimpleway:
I did. But I wiped and flashed again. No problems since.

Sent from my iPhone with the bigger Gee Bees.
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
hmm i wiped and reflashed about 5 times, still 100% awake.. weird
[EVO 4G Q&A, Help & Troubleshooting] theoner1:
No problem here phone is sleeping like it should. Using SteelRom rev I at the moment.
[EVO 4G Q&A, Help & Troubleshooting] aph:
Awake meaning the screen never turns off?

Spoken from my Evo using Ultra Keyboard and XDA App
[EVO 4G Q&A, Help & Troubleshooting] notasimpleway:
Try downloading the ROM again. You may have a bad download. Also, did you use Titanium Backup to install everything?

Sent from my iPhone with the bigger Gee Bees.
[EVO 4G Q&A, Help & Troubleshooting] lettcco:
try uninstalling apps that you recently downloaded. I had the same problem on a different rom, turns out it was something called sensorly map keeping my phone up.
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
its a fresh flash... no apps installed. i also tried steelrom, same behavior.... if i flash 3.30.x.x no,100% awake issues. any ideas?
[EVO 4G Q&A, Help & Troubleshooting] Compusmurf:
MarkGBE, WHAT particular item is keeping your phone in awake mode. Use some tool, like spare parts, and see what exactly is keeping it awake.

Report this info back and folks will be able to help you more.
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
not sure. looking in spare parts... i dont see anything with a ton of usage,.,.,.
[EVO 4G Q&A, Help & Troubleshooting] Compusmurf:
In spare parts, Battery History, Partial Wake usage, select Since Last unplugged.

If you're getting 100% wake time, whatever's holding it open will show there.

Leave it unplugged, turn the screen off and let it sit for awhile to gather up some statistics.
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
currently on the top of that list is 'Media' with 2m 47 sec. second is android system. 1min 56sec..
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
yeah this makes no sense... nothing appears to be keeping it awake...
[EVO 4G Q&A, Help & Troubleshooting] colonelfarva:
Just wanted to confirm that I have this problem using both most recent SprintLovers and Fresh. Even restoring from nandroid backup seems to keep it open. Fresh install, no apps. Driving me nuts.

Attempting to flash burnt droid now. Will report results.

EDIT: nada.

Using latest radios, etc. from this thread: http://xdaforums.com/showthread.php?t=715485

Also using burnt droid's kernel with less aggressive undervolting.
[EVO 4G Q&A, Help & Troubleshooting] Adam1422:
ever since...

ever since I flashed the latest radios my phone has not went to sleep. software version 3.30 and it also seems like my battery life has taken a dive for the worst. Any ideas?
[EVO 4G Q&A, Help & Troubleshooting] lovethyEVO:
You're close. It's actually pri 1.90 that's keeping the phone awake. Just revert back to 1.77 and it should sleep again.

Edit: pri 1.90 was the cause of my 100% wake time. I reverted to 1.77 to fix it but now I am going to test the latest radios versus the radios we upgraded from and also a combination of flashing new and previous radios together.
[EVO 4G Q&A, Help & Troubleshooting] snovvman:
I've also read that 1.90 PRI, coupled with 3.70 ROM causes no problems. It seems one must use 3.70-based ROM to run 1.90 PRI.

What ROM base are you using?

Edit: If you are in fact using 3.70, then I wonder if 3.70 and 1.90 need to come up at the same time? That is, if you flashed them out of sync, maybe you need to wipe and re-flash?
[EVO 4G Q&A, Help & Troubleshooting] Compusmurf:
Well, most of the romdev's all say not to do the new radios and pri if you're not on the new 3.70.x rom and not to mix and match kernels with it either.
[EVO 4G Q&A, Help & Troubleshooting] lovethyEVO:
I personally built the rom I am using with the 3.70 base. I also updated all the radios. When I reverted the pri thats when my wake issue dropped. But its fine. I will still test and then just keep whatever works for my rom.
[EVO 4G Q&A, Help & Troubleshooting] snovvman:
Thanks. Please do report back if you have new results.
[EVO 4G Q&A, Help & Troubleshooting] xlGmanlx:
and you checked partial wake lock and checked all time frames? Do you have tango installed?? try seeing if you can find something in spare parts or if that doesn't work wipe the caches and reboot
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
I haven't flashed any radios or anything.. hmmm.
[EVO 4G Q&A, Help & Troubleshooting] illogos:
I've seen odd behavior like this before after flashing 3.30.651.3 based SprintLovers. My battery life was normal, but my wake time was equal to my up time. I think it was related to Places being up in Running Services or wifi related. I killed all non essential services, toggled wifi off and on, and then it seemed to be fine. My wake time stopped increasing after that when I turned my screen on. Didn't have the problem appear again even after reboots.
[EVO 4G Q&A, Help & Troubleshooting] colonelfarva:
I have 0004 hardware and was just able to solve the issue...by reverting to completely stock kernel, 1.77 PRI, and stock sprint rom 3.70. Bummer, but guess I'll just hang tight until more's known about the 0004 hardware.

EDIT: Well, everything looked good but now I can't enable wifi. Will not let me check the box and just displays "Error". Searching has produced all sorts of results, mostly related to apps or a bad SD card (mine reads/writes fine).

Radio: 2.15.00.11.19

Software: 3.70.651.1

Kernel: 2.6.32.17, htc-kernel@and18-2 #15

PRI: Tried both 1.90_003 and 1.77

on stock sprint 3.70 rom.
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
I have stock everything and no go with 3.70...... I'm back at 3.29.... now and all is well.
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
This is so frustrating. Anyone have any other ideas? Completely stock 3.70.x.x rom stock radios... fresh flash after completely wiping everything... up time = awake time.
[EVO 4G Q&A, Help & Troubleshooting] willy900wonka:
Try reverting back to the previous ( 1.77) NV and PRI. It has worked for others. Get them here http://xdaforums.com/showthread.php?t=715485
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
im on baseband 2.15.00.07.28 and PRI version 1.40_003 currently. i must be confused on the whole radio and NV and PRI thing.. Are these not touched when flashing a rom or are they?
[EVO 4G Q&A, Help & Troubleshooting] MarkGbe:
ah HA!. upgraded to the latest radio and that fixed it. Son of a.
[EVO 4G Q&A, Help & Troubleshooting] fastfreddy7:
Ok, so mines rooted so no problems, but now my g/f is *****ing at me for updating hers with the new update because its killing her battery like crazy. I havent got a chance to look at it, but hers is completely stock and unrooted, and I m asssuming is having the same awake time problem. Any ideas? She doesnt want me to root it or anything.
[EVO 4G Q&A, Help & Troubleshooting] xlGmanlx:
Buy her something shiny
[EVO 4G Q&A, Help & Troubleshooting] fastfreddy7:
Thanks, thats helpful...
[EVO 4G Q&A, Help & Troubleshooting] xlGmanlx:
Nothing really you can do if she doesn't want to root, once you take an ota its a wrap so more than likely she has an app that is keeping her phone awake
[EVO 4G Q&A, Help & Troubleshooting] fastfreddy7:
Thats what I figured. Maybe its time to really push for a root. Can the new update even be rooted?