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.

Taking the risk of GB radiofor the sake of science.

Just talked to a friend from vzw, he told me that if something happened he will hook me up with a replacement for my tbolt.
I've been using gb radio since the 1st day it was leaked, i have no problems on my phone, just some random FCs but that's given.
Since we don't have a solid demographics on how many people got bricked, Im going to take the risk and see if i get bricked.
This morning i just got into a bootloop but looks like its just the battery giving false stats. Its been more than 6 hours now in my external charger and i assume battery doesn't hold charge anymore, Im going tommorow to vzw to have it replaced.
Question is, will logcat be enough to monitor my phone in case i got bricked so i can pull some important data regarding how it happen?, that way we can find a clue on how to fix a radio-bricked tbolt.

Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App

Wow. Very cool that you're willing to do this. Looking forward to seeing what you find out.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
From what I've read, that's not possible as the bootloop happens even booting into recovery.

kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Yes i have cleared my battery stats. My previous battery is now dead. I think i discharged it too much, now its not holding any charge. My phone still runs on gb bamf and loving my lockscreen. Will let you know if i get bricked.
Sent from my ADR6400L using XDA App

i too am sticking it through, im too in love with this to revert back.

yakitori2 said:
kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.
Click to expand...
Click to collapse
Lol you obviously didn't read his post. No risk involved.

I hope someone could shed a light to my questions.
1st. How does the radio firmware work on our phone? Does it work like a driver where it acts a mediator between the roms(software) to the phone's hardware.
2nd. What are the possible trigger to recreate the bootloop of death? There are some cases that my phone overheats because of non responsive apps and ever since i flashed on GB rom there i times i can feel my phone hot, which could be the case from some of the boot loop victim that they fried something inside their phone.
3rd. What are the chances that same bootloop of death could also occur in froyo radio? Just because vzw officially released the radio doesn't mean it has same risk like the leaked GB radio. It is like how HTC manufactured the phone, they tested most of it but some are still lemons.
Everything is in theory right now, there are no fix because it happens in random and the reason is still unknown. I'd choose to participate for the fix instead of waiting for someone to figure out the fix. We all do take a bold step in rooting our phone, flashing different roms, putting our faith on the battery that it wouldn't fail during the flashing process. Once we modified our phone from its stock settings we acknowledge the risk, and that risk is the one of the few factors the fuels the development of the rom/kernel community.
I've noticed several repacks of the GB radio:
http://www.multiupload.com/HU471CMQI0 ----
MD5: EE2A824E51CB148A2256F93E30A3B9F9
http://www.worldofjohnboy.com/dhemke17/ROMFiles/PG05IMGGB.zip ---- MD5: fda2a314975dd829b4e3611ecc8cfa13
PG05IMG_gingerradio.zip <- from http://forum.xda-developers.com/showthread.php?t=1082001 links alread removed. This is the same radio from androidpolice.com----
MD5: 52DD83AA40E30186C9FBEFAFD1BAB534
For the record, i flashed mine with the MD5: EE2A824E51CB148A2256F93E30A3B9F9
right now im using das bamf 2.0-5 running on imoseyon_leanKernel_v2.5.4GBtest6
Im keeping a close watch on my temp running on "extreme settings" 1.4ghz extremely undervolt.
SetCPU profile set to minimum setting when temp goes more than 97F

I just called verizon 611. My phone is not bricked and still functioning properly, but i told the operator that my phone constantly reboots( I pretended that my phone was bricked), i was passed to higher level tier support and they said they will be sending a new phone to me and there will be an extra envelop where i need to put my old phone to return to them. The call only took me 10-15 minutes and I believe VZW is aware that Tbolt has this issue even if its GB or the stock froyo rom.

i reverted back last night but i will def be back once things are more stable.. i already miss it

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.

[Q] Do Roms Fix Issues?

I'm thinking of getting an HTC Sensation, but I also read about the issues with lag, touchscreen being unresponsive, and the Wifi death grip.
I know the death grip isn't too much of an issue since it only happens if you hold it in a way that no normal person would, but would ROMs fix the lag and touchscreen issues?
Also, since I'm coming from a G1, I'm wondering if it's possible to root this phone and then, in case something happens, unroot it so I can stay under warranty?
Thanks

Customs roms will help in all those categories. I have no touchscreen issues though, that might be hardware related but I'm not too sure. Maybe a AOSP Rom or custom Rom can fix it. Get a Sensation, it will get unlocked soon and I have a feeling it will be a busy place in this section soon, hopefully

Awesome, how about unrooting? Is it possible with this phone? I usually am very careful with my phones but you never know...

Yes you can always go back to stock, choose one of the RUU roms
edit: here are the roms: RUU roms

I am using stock and unroot and I have not one issue.
Sent from my HTC Sensation using Tapatalk

insanechinaman said:
I'm thinking of getting an HTC Sensation, but I also read about the issues with lag, touchscreen being unresponsive, and the Wifi death grip.
I know the death grip isn't too much of an issue since it only happens if you hold it in a way that no normal person would, but would ROMs fix the lag and touchscreen issues?
Also, since I'm coming from a G1, I'm wondering if it's possible to root this phone and then, in case something happens, unroot it so I can stay under warranty?
Thanks
Click to expand...
Click to collapse
It's 2011 and you are still using a G1? LMBO you should of retired that phone 3yrs ago

nccu_eagles said:
It's 2011 and you are still using a G1? LMBO you should of retired that phone 3yrs ago
Click to expand...
Click to collapse
Lol, even if you have a sensation with those issues, it's still an upgrade

Being experienced in rooting and such, flashing custom roms usually knock out minor bugs that may dwell in stock software. If your dealing with a hardware issue you definitely won't have any luck flashing anything to address the issue, (Common sense right?). You always have the option to unroot your phone in case you have to shoot it back over to sprint. Granted I was able to take my OG Evo to a sprint kiosk fully rooted with CM7 and sell it for $150 to get the E3D. They might not give a ****.
Quote Edit-
nccu_eagles said:
It's 2011 and you are still using a G1? LMBO you should of retired that phone 3yrs ago
Click to expand...
Click to collapse
Don't dog the G1. That thing is like the godfather of droids. The start of it all.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!

r0cky0790 said:
Don't dog the G1. That thing is like the godfather of droids.
Click to expand...
Click to collapse
Not "dogging" the G1 that was my first android device back in 2008 but it's old!! I don't care what rom you're running that thing is a dinosaur
Sent from my HTC Sensation 4G using XDA App

nccu_eagles said:
Not "dogging" the G1 that was my first android device back in 2008 but it's old!! I don't care what rom you're running that thing is a dinosaur
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Hey hey it's still got quite an active development team! Got it running with Gingerbread like a champ too. That said, it really is time to retire the old geezer. Good times though.
Good to know about the rooting and everything. Got my Sensation today, and so far it's been a beast.

Keep in mind the issues reported are from a very small and likely not representative sampling of the population. There are a lot of folks who don't post that their phone works fine cause then they'd look silly. I'm one of them.
Sent from my HTC Sexiness.

[Q] G2X still automatically reboots after gingerbread update

I am totally new heree and not sure if this is the right place to post this. Please bear with me.
I updated my G2X when the Gingerbread version first came out. I just noticed that it still automatically rebooted itself twice last night while I was reading. The G2X was right nest to me and I heard the T-Mobile tone while it rebooted. Has anyone experienced this? I thought this update shall fix this bugging issue. I also notice the battery drains faster. Anyone knows how to root it after gingerbread update? Thanks.

traveljazz said:
I am totally new heree and not sure if this is the right place to post this. Please bear with me.
I updated my G2X when the Gingerbread version first came out. I just noticed that it still automatically rebooted itself twice last night while I was reading. The G2X was right nest to me and I heard the T-Mobile tone while it rebooted. Has anyone experienced this? I thought this update shall fix this bugging issue. I also notice the battery drains faster. Anyone knows how to root it after gingerbread update? Thanks.
Click to expand...
Click to collapse
A factory reset after I did the update has helped me avoid all issues.

tmo will replace it. you just need to speak with them and not the first person you get. The first person I think are outsorced and they will transfer you to tmo tech guys.

jimcarroll said:
tmo will replace it. you just need to speak with them and not the first person you get. The first person I think are outsorced and they will transfer you to tmo tech guys.
Click to expand...
Click to collapse
you mean calling customer service? or in store?

Yea get that ***** replaced. there are good ones out there you just need to find it..

Factory reset after the update fixed it for me to.

jabhome said:
A factory reset after I did the update has helped me avoid all issues.
Click to expand...
Click to collapse
Yup, go to the privacy menu and use the option.
The simple act of doing a reset does a lot for a smart phone.
I had an Iphone 3g where after 4.2.1 the solution to speed was to do 2 factory resets in a row.
Some people will return a laptop because they don't want to do a reboot.
------------After the reset, go to the marketplace and the first thing install the T-Mobile My Account app. The original version is problematic and can lead to buggieness

tombaker1 said:
Yup, go to the privacy menu and use the option.
The simple act of doing a reset does a lot for a smart phone.
I had an Iphone 3g where after 4.2.1 the solution to speed was to do 2 factory resets in a row.
Some people will return a laptop because they don't want to do a reboot.
------------After the reset, go to the marketplace and the first thing install the T-Mobile My Account app. The original version is problematic and can lead to buggieness
Click to expand...
Click to collapse
If you return a phone to Tmobile before doing a factory reset to see if it solves your problem then you simply don't value your time. A factory reset takes all but five minutes. If you call Tmobile you will have to wait for them to ship you a phone, and when it arrives it will be in "factory reset" condition anyway. If you go to a retailer and pick a replacement up, it too will be in the same condition. So if you are going to get a reset replacement, everyone would be wise to try a reset before rushing to Tmobile.

I had the same problems with GB after the update- I didnt do a factory reset though.
Moved to Eagles Blood and seems like a much more stable and cleaner rom- havent tested enough to see if it reboots or not though.

To root, flash clockwork mod recovery using nvflash and install a rooted rom. There's a rooted version of gb stock out there, or you could be adventurous and install one of the many custom ones we have.
Sent from my Nexus 3 using XDA Ultimate App

Return your broken phone ASAP. Phones should not randomly turn off or reboot. It is broken. Do not try to fix a broken phone on your own. It will result in nothing but headaches. Take it back now!

Yeah my replacement phone still randomly dies, I'll come back in a few hours and have to do a battery pull. It doesn't reboot like the old one but it does die more.
Should I get the replacement replaced?

Horsey said:
I had the same problems with GB after the update- I didnt do a factory reset though.
Moved to Eagles Blood and seems like a much more stable and cleaner rom- havent tested enough to see if it reboots or not though.
Click to expand...
Click to collapse
I ran Xboarders OTA GB with no tweaks since it came out. I then switched to EB 1.07 and had a ton of issues. I then returns to Xboarders OTA tweak and it was flawless. Now I am on to Weapon G2x.
Like I said, I really think a good scrub down and wipe, i.e. factory reset does wonders, at least folks should give it a try.

I absolutely agree that theres a good, actually great batch out there, I have NEVER had a single issue with my phone and its bone stock on 2.2.
Sent from my LG-P999 using XDA Premium App

so are you doing this in the store? or calling customer service?

So auto reboot issue is the only issue you people are facing in this mobile phone?

Returned phone . New works flawlessly. Tmo is aware of the issue. When u call you will talk first with an outsourced person. Get past them they will transfer u to tmo who will pretty much no questions asked process ur return
Sent from my LG-P999 using XDA App

Mine is still rebooting and having problems, i factory reset twice and still having issues. What should i do now?

same problem with my g2x and my wifes g2x...is there a solution for this?
I bought from ebay after reading reviews that the phone works find after gb update.....that means going back to tmobile is not an option for me
Sonic Marvel said:
Mine is still rebooting and having problems, i factory reset twice and still having issues. What should i do now?
Click to expand...
Click to collapse

Purchase at eBay does not affect 1-year warranty.