Database Info

So after living with official Froyo for a month...

How has your experience been with it?
Mine has been fine, my wife's not so much...
My wife's Captivate: WAS very very laggy but 2.2 fixed it. She had zero problems with her GPS but the 2.2 update threw it off about a block : /
My Captivate: Just as smooth as before, and GPS is perfect as was before.
How are you guys enjoying Froyo?

Not quite sure what you mean. I didn't know there was an official one for the captivate sent out? Searched for it and couldn't find it on google. You sure ATT pushed out official 2.2 a month ago?

There is no official froyo yet for the captivate
Sent from my SuperDuper!Captivate | PHOENIX RISING 4.1 | Firebird 2 v0.4 | Member of Team Phoenix

There is through Rogers.

gunstar3035 said:
There is through Rogers.
Click to expand...
Click to collapse
Correct... Rogers has released their update.
Us down here in the U.S. are still speculating when/if ATT will ever update our devices
Sent from my SAMSUNG-SGH-I897 using XDA App

I have lots of shutdown issues right now, gonna flash to a custom rom to see if it makes a diff.

Eschatologist said:
I have lots of shutdown issues right now, gonna flash to a custom rom to see if it makes a diff.
Click to expand...
Click to collapse
Flashing a new rom will not fix the problem...your only option is to contact att and get a replacement phone
Sent from my SAMSUNG-SGH-I897 using XDA App

Smallsmx3 said:
Flashing a new rom will not fix the problem...your only option is to contact att and get a replacement phone
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
+1 I had to do this and I'm glad I did, 30 days with zero random shutdowns.
Sent from my SAMSUNG-SGH-I897

DeMarzo said:
Correct... Rogers has released their update.
Us down here in the U.S. are still speculating when/if ATT will ever update our devices
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sorry I should have specified Canada : /
It is complete bull$hit that ATT has not given you guys 2.2 I think I would go custom ROM and be done with it.

Just get a new (not refurbished) Captivate instead!
Eschatologist said:
I have lots of shutdown issues right now, gonna flash to a custom rom to see if it makes a diff.
Click to expand...
Click to collapse
Get another phone. Do not settle on a defective phone. I spoke with someone in the "Office of the President" (a higher level of AT&T customer service) and after checking into the issue, they overnighted me a NEW Captivate (my phone was purchased in August, so I am well out of the 30-days). Their statement was that the defective phones are not supposed to be in the new lots or refurb lots, as it is against their procedures to knowingly sell defective phones. I would suggest taking your complaints there. The number is 1-800-331-0500. Be firm and upset, but be respectful. They will work with you.

Overall its not bad, but I do have a few issues I am still contending with.
When I first did the update I lost navigation all together. I restarted the phone (using a access number Samsung provided me) and solved that issue.
I lost a lot of files that were on my SD card. I haven't been able to figure out why that should be. It's like the update made a point of deleting everything except my media... Oh well
However I am still fighting issues with the both the home and car docks. (Which by the way Samsung Canada doesn't recognize up here and said I am on my own)
The usb audio out worked once and then disappeared on me altogether... Restarting apps and phone isn't helping...
And using the home dock, the phones main screens get stuck in landscape mode (only after doing it all night, if it's only running for a couple hours it's fine) and I have to shut off the phone to get it back to normal. Using Samsung home dock app it was every night. Alarms Plus as well. I am currently using an app called no dock and its down to 25% of the time I don't get stuck in landscape mode. Livable... The car dock I have not gotten stuck in landscape yet, but then I don't think it will ever be in the dock long enough to get stuck...
Which brings me to a point of frustration. Why isn't landscape mode functional outside the dock mode? I love the ability, just not getting stuck there until I reboot... The phone CAN and WILL do it on certain conditions, so why not all the time?
I haven't tried the mass storage mode or tethering yet so I don't know if they are working or I have more issues to deal with.

Going back to Gingerbread.

I was about to make the jump back to Gingerbread "I.e. The ROM/Radio of death" and just wanted to know how many people have gotten over the bricking debacle.
I have yet to hear of anyone who has had a bricked device since a day or two after the incident was brought up.

Ya, I'm starting to think this may have had alot to do with just user error. I remember back in the early days of rooting when people used to brick phones because they didn't know what they were doing.
I think I'll wait another week and if I don't hear of anymore "bricks" I may switch back to GB.

Dnakaman said:
Ya, I'm starting to think this may have had alot to do with just user error. I remember back in the early days of rooting when people used to brick phones because they didn't know what they were doing.
I think I'll wait another week and if I don't hear of anymore "bricks" I may switch back to GB.
Click to expand...
Click to collapse
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.

bp328i said:
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Interesting, thats actual enough for me to hold off till a future release. I had a friend who got bricked but had little Android/Rooting knowledge so I kind of blew it off as it must have been user error. Thanks for the heads up, and will now continue waiting for a new release. Damn.
Edit: Did you have any luck getting a replacement from Verizon?

bp328i said:
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Man, that sucks. I know I've seen you post about the issue, but you seem to be the only one that actually has this issue that has actually posted anything concrete here.
Others that have posted about "bricks" sounded like they just didn't know what they were doing and were actually recoverable.
But like Mike said, enough for me to wait until more evidence is uncovered.
Thanks for the info.

miketoasty said:
Interesting, thats actual enough for me to hold off till a future release. I had a friend who got bricked but had little Android/Rooting knowledge so I kind of blew it off as it must have been user error. Thanks for the heads up, and will now continue waiting for a new release. Damn.
Edit: Did you have any luck getting a replacement from Verizon?
Click to expand...
Click to collapse
And to add to the above I do all my rooting via adb, I have never used a one click root. I'm also an Official Themer on another forum, so I know my way around Android a little.
I had insurance that made me send it off to try to have it repaired first. I just got a new one yesterday.
I'm waiting on a new Gingerbread radio to come out before going back to Gingerbread even though how much I miss it.

Well right before the news was posted, I noticed some connection issues, it was kind of a weird issue. So I reverted back right after seeing the brick thread....
SCARY!

I was just about to make a thread similar to this. Seems as though the bricking phenomenon has blown over. I just flashed gingeritis beta IX and I'm loving it!

bp328i said:
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Question for you. Did you have a third-party or extended battery in it?

want a droid said:
I was just about to make a thread similar to this. Seems as though the bricking phenomenon has blown over. I just flashed gingeritis beta IX and I'm loving it!
Click to expand...
Click to collapse
It's blown over because most everyone went back to froyo. Nothing has actually been resolved.

Jaxidian said:
Question for you. Did you have a third-party or extended battery in it?
Click to expand...
Click to collapse
Nope, stock battery and charger.
Sent from my ADR6400L using XDA App

SirVilhelm said:
It's blown over because most everyone went back to froyo. Nothing has actually been resolved.
Click to expand...
Click to collapse
This is what I figured.

A lot of people stayed on gingerbread though with no more reports of bricks...
Sent from my ADR6400L running Gingeritis v1.0 Beta IX

want a droid said:
A lot of people stayed on gingerbread though with no more reports of bricks...
Sent from my ADR6400L running Gingeritis v1.0 Beta IX
Click to expand...
Click to collapse
I think that is where the real problem is.
The issue is so random, there is no set explaination at this time to explain why/how it happened.
Since the one person that I know of sounds like a very creditable person based on feedback on these forums, I myself am going to error on the side of caution.
I was running GB with no issues as well, but I would hate to kill my phone, just because I "thought" it was safe to reload GB.

I have been on BAMF since they came onto the TB scene. Less than a week from phone release I rooted and started rom'ing. I loaded the new ginger radio about a day before the first report of the brick came out. I havent had any problems. But I have been keeping my eyes open to see when or what will cause a brick so every two seconds I cheack my phone BUT i can't post in the development forum yet So i gotta wait till ten UGH

i'll wait for our developers to give the thumbs up on going over to GB roms, whats the rush vs the risk? Not a big deal to wait another week or two considering what u could be going thru. BAMF remix 1.7 is running flawlessly for me after I dropped back from GB.

I was using Gingeritis from Beta 3 to Gingeritis IX. Honestly, I haven't had a single random reboot or any problem at all.
However, I did have a data issue. If my phone would change to a 3g signal, it wouldn't bring back 4G. But, once I rebooted the phone one time, the problem was fixed from there on.
I still have Gingeritis IX on my phone, and its great. I'm running Imo's test6 kernel as well.

miketoasty said:
I was about to make the jump back to Gingerbread "I.e. The ROM/Radio of death" and just wanted to know how many people have gotten over the bricking debacle.
I have yet to hear of anyone who has had a bricked device since a day or two after the incident was brought up.
Click to expand...
Click to collapse
Honestly the bricking thing threw me off first, then I noticed it takes forever to charge, drains quicker and camera and camcorder sucks on gingerbread. So I'm sticking on froyo Bamf for awhile.

Yeah I'm back on froyo. And to those who are "watching my phone and no signs of bricking", there will be no signs. You'll pull your phone from your pocket and have a bootlooping phone, unfortunately. I'm running CM7 gb, 95% of things work like they should, and since it's a froyo radio, I'm immune to the brick of death.
Sent from my ThunderBolt using XDA Premium App

Jaxidian said:
Question for you. Did you have a third-party or extended battery in it?
Click to expand...
Click to collapse
Hmmm... I was wondering this myself. I'm on GB BAMF 2.05 and only have random reboots when I have my 3rd party battery in. The stock battery doesn't seem to have any issues.

Ics 4.04 hopefully to us too

http://www.xda-developers.com/android/galaxy-nexus-gets-ics-4-0-4-update/

We'll most likely get it once the sources are updated to 4.0.4. It looks like a lot of things have changed in this build too. Maybe performance will increase on our phones?

Source has been pushed.
Sent from my Amazon Kindle Fire using Tapatalk 2 Beta-4

dw9906 said:
Source has been pushed.
Sent from my Amazon Kindle Fire using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
ok guys its here Whitehawkx AOKP 29 is android 4.0.4 maybe its just me but it seems a lot smoother

I just like the fact that multitouch was updated in it for the keyboard issues I was having... Typing drunk on CM9 was messing with everything I needed lol.

Anyone know when the OTA will be out
Been trying different ROMs but then my phone started random rebooting even when I put it back to completely stock and re-locked it. So, I sent it in for replacement. Now my replacement phone at the top of the screen used to say "T-mobile" but now just reads "LG" on the glass. I guess the later phones were no longer branded T-mobile.
One thing I noticed though is when I put in a ROM that worked flawlessly on my old phone it would cause the replacement to have random reboots, force close, and just plain lock up where I would be required to remove/replace the battery to get it to work again. Any ideas or suggestions??? I have only been able to run the stock GB rom successfully.
Any ideas on what the phones issue may be?? Or maybe when the OTA for a stock ICS will be available?
Thanks,
NotinStock

notinstock said:
Been trying different ROMs but then my phone started random rebooting even when I put it back to completely stock and re-locked it. So, I sent it in for replacement. Now my replacement phone at the top of the screen used to say "T-mobile" but now just reads "LG" on the glass. I guess the later phones were no longer branded T-mobile.
One thing I noticed though is when I put in a ROM that worked flawlessly on my old phone it would cause the replacement to have random reboots, force close, and just plain lock up where I would be required to remove/replace the battery to get it to work again. Any ideas or suggestions??? I have only been able to run the stock GB rom successfully.
Any ideas on what the phones issue may be?? Or maybe when the OTA for a stock ICS will be available?
Thanks,
NotinStock
Click to expand...
Click to collapse
1. why are you posting in this thread?
2. some roms/kernels are undervolted, if your phone cant handle it youll get random reboots.
3. nobody knows when ICS will get here, NOBODY. if anyone says they know when it will get here, they are lying. there are no exceptions, EVER!

Loving all the improvements that come with this update. I just installed AOKP build 31 and have had zero issues thus far. Just one thing missing...can't hangout in G+ and we know whose fault that is. Nvidia

[Q] Why have my ringtones and music app gone haywire? (Problem Fixed)

My phone has never been rooted or had a custom ROM installed. I haven't really done anything to it since I got it really.
It's running Android version 4.0.4 and Kernel version 3.0.8
About a week ago I noticed that when I opened the 'Music play' app that came with the phone, under the 'All' files view, every MP3 was showing triples of each. I unmounted the SD card and removed all the MP3s from USB storage, restarted the phone, and that problem was gone.
A day or so later I noticed my phone wasn't ringing when I got a call and none of my notification ringtones were working. When I looked in Settings -Sounds - Phone Ringtone, I saw that all the custom ringtones I had that didn't come with the phone were listed in triplicate. I removed them all from the phone and have restarted it a couple of times, but even though they're not on the phone anymore they're still listed in triplicate.
Anyone ever heard of this issue and what do y'all think will be the solution to get things back to normal?
I appreciate anyone that takes the time to respond. Thanks. :good:

From what I remember there isn't any permanent fix. They always come back.
Just so you know we have official jb. Use kies to get the update.
Sent from my HTC One using Tapatalk 4

xcrazydx said:
Just so you know we have official jb. Use kies to get the update.
Click to expand...
Click to collapse
official jb = official jail break?

Sayre said:
official jb = official jail break?
Click to expand...
Click to collapse
Jelly bean
Sent from my HTC One using Tapatalk 4

Sayre said:
official jb = official jail break?
Click to expand...
Click to collapse
I first thought you were joking, but then realized you were serious, lol

I had no idea what he was saying and I'm not ashamed to admit it. I've never had the desire to root my phone or any of that stuff, and I don't know a lot of the terminology or acronyms that well.
But anyway, I fixed the issue. The problem occurs from not 'Ejecting' the phone from Windows when you've been accessing the USB or SD card storage thru your PC or laptop. I noticed that when I would connect my USB cable to the phone, and box would pop up saying that it had detected errors on one of the drives and asking me if I wanted to scan the drive and fix them. I did the scan/fix and the problem has gone away.

For now. They will all come back.
Sent from my HTC One using Tapatalk 4

[Q] (Q) [HELP] App2SD work on Infuse? If so, Which build?

Hi there. This is my first post on forum. I searched around before asking and couldn't come across anything. My apologies if i overlooked anything.
Here's a short run down of the prob. Purchased a infuse off ebay. Phone received on initial purchase worked with app2sd and google hangouts (must haves for me). However, due to faulty speaker, i had to return. Replacement was different. Gui interface and just everything in general. That's when i learned it was a different OS/Rom as you guys would say.
So i searched around and found kies mini and updated to gingerbread. That fixed my problem with google hangouts which is now working fine. Though, App2sd is still not working and gives me the same ole "failed to move application", "not enough memory" error. Was wondering what solution you all could offer?
Should i go back to froyo that it was shipped with and upgrade to another OS in hope i can use my app2sd again?
And Is it okay to upgrade ICS/JB/ or beanstalk from 2.3.6? Do i need to revert to stock first? if so, direction please?
Should also note, that my phone was fubared on first upgrade to gingerbread. "/\ firmware encountered an issue /\" error. Is that what you guys refer to as a bricked phone? Was stuck on this screen and recovery mode failed around 2 times before working like a charm 3rd time around. So i'm now somewhat hesitant to do anything more in terms of upgrading. I do have 60 day warranty with ebay, so i'm not all that worried. Though, simply wanted some advice/direction before i made any drastic attempts at anything else next time around. Thx to those replying. Appreciate any help or support on this.
FIRMWARE: 2.3.6 (not rooted)
BASEBAND: I997UCLB3
KERNEL VERS. 2.6.35.7-I997UCLB3-CL977492
BUILD: GINGERBREAD.UCLB3

I would say that it would be best to flash CyanogenMod or Beanstalk along with gapps and you can move the apps to the SD card by using the settings.
Sent from my One XL using XDA Premium 4 mobile app

magnetboard said:
I would say that it would be best to flash CyanogenMod or Beanstalk along with gapps and you can move the apps to the SD card by using the settings.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ya...I got a beer in me, next thing you knew i was fiddle ****n around with files lol. Thx. Things are better now. 12 hrs later and i'm finally running beanstalk. Hangouts and app2sd apps are working. For now....lol +++
That was all i really wanted. New to smart phones. Sure there's a **** ton more i've been missing out on. Welcome to new technology kcajoc! Been enjoying my flip phone for the last 5yrs hahahahah.
Ps. Thanks again to everyone who made this possible! Truly a wonderful forum you guys got here! A lot of informative stuff and great reading i'm finding here.
???my thanks meter is still at 0. I've hit it several times today. Shrugs???

Issues so far on my new build:
*Battery is being depleted quickly. went from 98% down to 90% in a matter of minutes.
*Wi-fi keeps dropping. Keeps saying no connection.
Ideas anyone? Thanks.