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

Root Where is the fix for GB?!

Proof of this statement??

Sorry I miss typed,what I meant to write was most owners who are unhappy with gingerbread, just want there old phone back....but now that you mentioned that it made me think a bit..... In my circle of friends we have 6 droid X's. 3 of them are back on froyo,and 2 of the 3 on GB are running bone stock phones,and want froyo back but are afraid to void there warranty on there phones,they are living with the poor battery life,and dropped 3g..we ALL tried gingerbread,some of us the leaks,but all of us the OTA,and many replacements after....only 1 of us is on GB,and happy,and that phone is on a custom GB rom.....so sorry I didnt clarify....
For furthur proof that the gingerbread roll out has been very bumpy is the fact that motorola/verizon are out of replacement phones! They have no droid xs to give out,they are giving droid x2s out (which BTW are on froyo)...
 
All the proof you really need to know that enough people are having issues with GB on the DX is the fact that an update to fix said issues is being worked on as we speak.
 
For furthur proof that the gingerbread roll out has been very bumpy is the fact that motorola/verizon are out of replacement phones! They have no droid xs to give out,they are giving droid x2s out (which BTW are on froyo)...

personally i find that to more likely show that the phone is no longer in production and is being officially replaced as a model...

and yes the X2 is on Froyo...because it came out before Moto had released GB to any phone yet...and if our Froyo update proves anything we should all know how long it takes Moto to get updates out...they announced out Froyo update the day the phone was revealed...and it took them MONTHS to get it to us...

the thing is...and what i find so comical about the vocal minority of users having issues with GB, is that they seem to have such short memories...maybe they were not around for the initial Froyo update...maybe they didn't get their X's until after Froyo was updated...but they pretend like Froyo was so perfect...ignoring all of the problems that some people had on Froyo

All the proof you really need to know that enough people are having issues with GB on the DX is the fact that an update to fix said issues is being worked on as we speak.

that is not really proof of anything...its only proof that things could be improved...and that is always true...

the Honda Accord is universally recognized as one of the best cars in the world...

Honda is most certainly working on a 2013 model as we speak...is that any proof that the majority of 2011 Accord owners wish they could have their 1999 Accord's back?
 
Sorry I miss typed,what I meant to write was most owners who are unhappy with gingerbread, just want there old phone back....but now that you mentioned that it made me think a bit..... In my circle of friends we have 6 droid X's. 3 of them are back on froyo,and 2 of the 3 on GB are running bone stock phones,and want froyo back but are afraid to void there warranty on there phones,they are living with the poor battery life,and dropped 3g..we ALL tried gingerbread,some of us the leaks,but all of us the OTA,and many replacements after....only 1 of us is on GB,and happy,and that phone is on a custom GB rom.....so sorry I didnt clarify....
For furthur proof that the gingerbread roll out has been very bumpy is the fact that motorola/verizon are out of replacement phones! They have no droid xs to give out,they are giving droid x2s out (which BTW are on froyo)...

i had poor battery at first but then i just messed with it and it works fine now... they have a new battery manager jsut mess it with it mine works great now
 
Sorry I miss typed,what I meant to write was most owners who are unhappy with gingerbread, just want there old phone back....but now that you mentioned that it made me think a bit..... In my circle of friends we have 6 droid X's. 3 of them are back on froyo,and 2 of the 3 on GB are running bone stock phones,and want froyo back but are afraid to void there warranty on there phones,they are living with the poor battery life,and dropped 3g..we ALL tried gingerbread,some of us the leaks,but all of us the OTA,and many replacements after....only 1 of us is on GB,and happy,and that phone is on a custom GB rom.....so sorry I didnt clarify....
For furthur proof that the gingerbread roll out has been very bumpy is the fact that motorola/verizon are out of replacement phones! They have no droid xs to give out,they are giving droid x2s out (which BTW are on froyo)...

its very easy to go back to Froyo if that is what you want to do.
 
All models can tend run into trouble when upgrading OS's. IMO, this is the phone's most vulnerable time, as something can tend go wrong. What I think about is all the upgrading people, who not rooted, have no idea what to do to help stabilize a new build.
 
Nothing is keeping people from rooting their phone and going back to an unrooted FroYo.. can't wait till the "GB is broken" threads cease
 
My phone reboots VERY often, and can no longer be used to play mp3's from the SD card. Attempting such causes the phone to freeze and then reset.
Also (not sure if it's related) When I try to boot into recovery mode (hold home + power) I get an android with an exclamation point. Nothing else. Doesn't boot, have to battery pull.
I'll take that GB patch please...


Edit: Apparently I'm dumb and the process to get to/use recovery mode is different in GB. So retract that statement

Edit2: I chose to hide cause I can't figure out how to do strike-through :p
 
That sucks, but I can live with it. My biggest issue is having to reboot 3 or more times a week because it looses cell connection and won't get it back without a reboot. Never had that problem on Froyo. And that's a much bigger issue for a phone than camera settings. Especially if I'm home and on WiFi, I can (and have) lost cell connection, but had no idea because data still works fine on WiFi. But if someone tries to call me, they can't reach me, and I have no idea that anyone was trying to get a hold of me. This really needs to get fixed with the quickness.

Agreed that this is a really bad problem. Unfortunately, I've not found the custom ROM's to be any better. Apparently, it's an issue with the radio...the .12p baseband has this problems. The previous radio, .07p did not. Still trying to work out a fix but I've found a number of people having this problem with GB and it's various ROM's.
 
Agreed that this is a really bad problem. Unfortunately, I've not found the custom ROM's to be any better. Apparently, it's an issue with the radio...the .12p baseband has this problems. The previous radio, .07p did not. Still trying to work out a fix but I've found a number of people having this problem with GB and it's various ROM's.

Maybe you should try Roms with the .07 radio, l like CM7.
 
Maybe you should try Roms with the .07 radio l like CM7.

Cool, didn't realize that, I'll give it a try.

One note though, this isn't in the root section.

These threads will cease when Moto steps up and fixes the problem.
 
Overall Gingerbread is the most stable, least buggy update for the Droid X to date. The Froyo update was plagued with tons of massive bugs, all of the recognized (ie none of the one-time-fluke-sucks-to-be-you bugs) are very minor. The only bug I have experienced on Gingerbread is that it frequently won't stay off when I turn it off. After a minute or two of sitting untouched it will spontaneously start itself, however, I would classify this a far better the Froyo random rebooting issues.

Please stop complaining about GB, it is a very solid update, and if you have big issues with it, DON'T JUST LIVE WITH IT, take it in to Verizon for a replacement, because that is not par-for-the-course on this update.
 
I just sbf'd and installed CM7, baseband is BP_C_01.09.12P. Hmmm

screenshot-1312223134506.png
 
Overall Gingerbread is the most stable, least buggy update for the Droid X to date. The Froyo update was plagued with tons of massive bugs, all of the recognized (ie none of the one-time-fluke-sucks-to-be-you bugs) are very minor. The only bug I have experienced on Gingerbread is that it frequently won't stay off when I turn it off. After a minute or two of sitting untouched it will spontaneously start itself, however, I would classify this a far better the Froyo random rebooting issues.

Please stop complaining about GB, it is a very solid update, and if you have big issues with it, DON'T JUST LIVE WITH IT, take it in to Verizon for a replacement, because that is not par-for-the-course on this update.

Actually you are the one complaining. We are just reporting our experiences and trying to get a fix, what baseband are you on?

How do I downgrade to .07? I'm on Cm7?
 
Actually you are the one complaining. We are just reporting our experiences and trying to get a fix, what baseband are you on?

How do I downgrade to .07? I'm on Cm7?

I just sbf'd back to 2.3.340 and installed CM7 as you you are supposed to and I've been on .07 ever since.

I believe there is a post somewhere around here that has a flashable zip file that can get you on .07, there is also one for .12, but you are looking for the .07 of course.

Try looking for it with the search function, you may find it.
 
Here's mine, I'm going to try running CM7 with the .12 baseband and see if I lose connectivity. If I do lose connectivity, I'd like to revert to .07 if possible, any ideas?

CAP201108011238.png
 
Here's mine, I'm going to try running CM7 with the .12 baseband and see if I lose connectivity. If I do lose connectivity, I'd like to revert to .07 if possible, any ideas?

https://lh3.googleusercontent.com/-...AAAAAAPg/220oW5UkECY/s144/CAP201108011238.png

I'm curious, you were on GB right? Did you use the Monster.zip file by TBH to get to CM7, or did you sbf to 2.3.340 and then use the Monster.zip file, or did you sbf and go the cvpcs method???

EDIT:
Did you flash the monster zip twice as the directions say to do (assuming you used the Monster.zip file)?
 
Back
Top Bottom