• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

All Things Froyo

Not that I really thought the update would help it, but the random shut off still happens. Just started back up the old keep captivate alive app.

It is in that range of numbers...I will have to see if ATT will replace now.

But so glad my captivate has 2.2...very smooth thus far!!!
 
Just updated my phone thru kies mini without any problems...checked the quadrant scores ..now its showing 994. Previously it showed 750 on 2.1.
 
^It means nothing really. Those aren't an accurate display of how fast the phone is. The Nexus One didn't have severe lag, but it was lower than the Galaxy S on the quadrant results. It's just numbers really...

Big Pope Daddy said:
Not that I really thought the update would help it, but the random shut off still happens. Just started back up the old keep captivate alive app.

It is in that range of numbers...I will have to see if ATT will replace now.

But so glad my captivate has 2.2...very smooth thus far!!!
Click to expand...

Yeah, I think that was a hardware issue and not a software issue. Getting the phone replaced is probably the only option to fix that.
 
drapacioli said:
Yeah, I think that was a hardware issue and not a software issue. Getting the phone replaced is probably the only option to fix that.
Click to expand...

Figured I had held out this long...but I will call att today and see what direction they send me. Wanted to see how the 2.2 was before I stayed with the captivate just in case. I love the phone, seems quick as all get out now, so I think I will roll with it for awhile....well, hopefully a phone where it doesn't shut off!! LOL!
 
I'm doing the update thru Kies Mini, I got past the first download with the binary files but now I'm stuck at 16% on Kies and just a blue screen on the phone.. is this ok?
 
For those of you guys who are flustered at the apparent missing RAM on our phones - as a comparison to the Galaxy S (for which the Captivate is based on), it turns out that there is only about 384 MB of DDR RAM built into the Galaxy S. There is an additional 128 MB oneNAND chip and a 512 NAND ROM chip. This is all from the Galaxy S teardown found here: Galaxy S Teardown

It's likely that it was marketed as a 512 MB device because of the ROM (which is quite underhanded) but Samsung will probably never confirm this.

Now it might happen that Samsung actually built in 512 MB of working DDR RAM and there's something that's just eating up that extra 128 or so MB that is conveniently not showing up.

... I'd wager and say that the phone doesn't actually have 512 MB of usable RAM.
 
kaepos said:
For those of you guys who are flustered at the apparent missing RAM on our phones - as a comparison to the Galaxy S (for which the Captivate is based on), it turns out that there is only about 384 MB of DDR RAM built into the Galaxy S. There is an additional 128 MB oneNAND chip and a 512 NAND ROM chip. This is all from the Galaxy S teardown found here: Galaxy S Teardown

It's likely that it was marketed as a 512 MB device because of the ROM (which is quite underhanded) but Samsung will probably never confirm this.

Now it might happen that Samsung actually built in 512 MB of working DDR RAM and there's something that's just eating up that extra 128 or so MB that is conveniently not showing up.

... I'd wager and say that the phone doesn't actually have 512 MB of usable RAM.
Click to expand...

That did cross my mind as well. But I thought by now it would have been discovered and I don't see Samsung blatantly lying about something like this, because that's grounds for a lawsuit.
 
Having issues with my phone.

Installed Mini Kies
Connected the phone- downloaded and installed the update. The whole process took a while.
Disconnected from my comp and the phone restarted.

The ATT animation comes up
The Samsung animation comes up
then the phone goes black

After that there are random vibrations.

I've taken out the battery and restarted several times. I've waiting a long time for the home screen to come up and nothing happens. Also tried calling the phone and it does not buzz.

Any suggestions? Is my phone bricked?

Also- I'm unable to get my computer or Mini Kies to recognize the phone at this point. Otherwise I'd consider a reinstall.


Thoughts?
 
I think I may be SOL with the official Froyo update if there is no OTA option (after waiting so long, what a bummer)!

At home we're running Ubuntu (Meerkat) and it doesn't look like I can install Kies except on a Windows box. Will Wine be able to help me? Has anyone had success with that?

I might be able to use my work laptop (Windows) if all else fails & uninstall as soon as the update is successful... OR I can just take the plunge and root and install a custom ROM like a good number of you here...
 
Question for people who are getting black screens. Were your phones rooted and/or had a custom rom, whether or not you removed them before the update? Some Custom roms and root operations can screw with the settings that the update assumes is in place, and that in turn can lead to errors and ultimately a bricked phone if not properly rolled back before an update. At least, that's how it was explained to me when I was considering it. I really didn't want to test that theory...
 
emergency recovery isnt working.. its bricked isnt it?? any tips?

I bought the phone rooted but did a restore since then, I was under the impression that that would unroot the phone.. right?

Either way, it's not doing anything. Emergency Restore isn't working and if I try to restore from power off I get a "phone-irange triangle with a !-computer" logo on the screen and thats it.
 
Although the update was without incident for me, I think we're seeing to many "black screen" phones and other problems that is going to lead to AT&T pulling the update and going back to the laboratory.

I updated before the problems starting appearing, but if I had seen some of these results I wouldn't have pulled the trigger. :eek:
 
Man. I'm excited to update but... I'm gonna have to sit on this for a while and see if those with bricked phones can get 'em up and running. A fixable failure is relatively tolerable since it won't completely ruin the phone. A complete bricking of the phone, however... not so much.
 
angler87 said:
Having issues with my phone.

Installed Mini Kies
Connected the phone- downloaded and installed the update. The whole process took a while.
Disconnected from my comp and the phone restarted.

The ATT animation comes up
The Samsung animation comes up
then the phone goes black

After that there are random vibrations.

I've taken out the battery and restarted several times. I've waiting a long time for the home screen to come up and nothing happens. Also tried calling the phone and it does not buzz.

Any suggestions? Is my phone bricked?

Also- I'm unable to get my computer or Mini Kies to recognize the phone at this point. Otherwise I'd consider a reinstall.


Thoughts?
Click to expand...


My phone was having the EXACT same issue. I talked to Samsung support and they told me to reboot the phone while holding the volume up, volume down, and power buttons for 15 seconds as you power on. It will bring you to a admin screen. Choose "clear user data" (I lost my apps but not my contacts/media). Then choose to "reboot" the phone. I am now up and running Froyo... and beginning to reinstall all my apps.
 
Question for those that have had difficulty with the download . . . . did you use a 64 bit computer to perform the download? Although SOME 64 bit computers are recognizing the phone, there may be a compatability issue here. My Win 7 64 bit laptop recognized my phone SOMETIMES, so just to be safe I used my older Vista 32 bit laptop to perform the download.

Might not have anything to do with it . . . just asking.
 
rpddlvry21 said:
My phone was having the EXACT same issue. I talked to Samsung support and they told me to reboot the phone while holding the volume up, volume down, and power buttons for 15 seconds as you power on. It will bring you to a admin screen. Choose "clear user data" (I lost my apps but not my contacts/media). Then choose to "reboot" the phone. I am now up and running Froyo... and beginning to reinstall all my apps.
Click to expand...

Cleared the user data and restarted- still getting a black screen. I'm on the phone with Samsung now. Will post how it goes.
 
gary1949 said:
Question for those that have had difficulty with the download . . . . did you use a 64 bit computer to perform the download? Although SOME 64 bit computers are recognizing the phone, there may be a compatability issue here. My Win 7 64 bit laptop recognized my phone SOMETIMES, so just to be safe I used my older Vista 32 bit laptop to perform the download.

Might not have anything to do with it . . . just asking.
Click to expand...

I used 64 bit Win 7 Home Premium on my desktop, exactly followed ALL the instructions on the SAMSUNG website for installing the Kies program and the drivers (after uninstalling the old drivers I had been using) and had no problems. Kies saw the phone immediately and the update button ungreyed itself, the install took about 10 minutes and appears to have gone flawlessly.
 
rpddlvry21 said:
My phone was having the EXACT same issue. I talked to Samsung support and they told me to reboot the phone while holding the volume up, volume down, and power buttons for 15 seconds as you power on. It will bring you to a admin screen. Choose "clear user data" (I lost my apps but not my contacts/media). Then choose to "reboot" the phone. I am now up and running Froyo... and beginning to reinstall all my apps.
Click to expand...

this worked perfectly for me! thanks you!
 
Went perfectly smooth with my update. I did have to take it back to TouchWiz before I could get Mini Kies to recognize my device. I use Zeam and it would not hook up for some reason.
 
You must log in or register to reply here.
Back
Top Bottom