Database Info

[Android] Motorola Backflip - DON'T BUY, HERE'S WHY!

OK, so I've been using a Kaiser/Tilt with Eclair on it for awhile. I've spent countless hours drooling after the Nexus One. When AT&T finally got the "Backflip" from Motorola, I just couldn't resist. I took the plunge.
I should've known better. I have plenty of AT&T horror stories, and this is the same carrier that wont allow you to tell your Java apps NOT to ask for permission more than once (making Opera mini a PITA but the only usable browser for non-smart-phones).
There is NO option to install applications from untrusted sources. This means anything on your SD card, downloaded from the web or over your wifi at home WILL NOT WORK. Naturally, you also cannot use the "su" command in terminal.
Motoblur is nice I guess, but the uninstallable AT&T paid apps, the limitations of 1.5 firmware (ie: no google navigator, no voice search) and the locked-to-yahoo-search-bar are enough to get me to say NO to any further AT&T abuse.
With the Kaiser's bloatware, they removed/hid apps from you so you wouldn't try to use them and replaced them with their crapware.
AT&T does not know the meaning of "open" and they do not understand Android. You are not buying an Android phone when you buy from AT&T.
You are buying a device LOCKED to a market with a smaller number of applications than the iPhone (I don't use Apple products either ) forced to use a lesser search engine for your most convenient option and subject to losing any application that was once on the market but then removed. You can't install your own apps or even test them on your device. Period.
Also on my first day of using it I got a number of "Force Close" messages including on the built-in applications (ie: Motorola's flavor of the desk clock).
It's decent hardware, it feels pretty zippy to me, but this is exactly why I WONT buy an iPhone.
Screw you, AT&T. I will make sure that everyone I know is properly informed about this crippled device that is nothing like the Android experience is supposed to (expected to!) be.
/endrant phew, going to go breathe for awhile.
EDIT: I will add:
- Set "orientation" on this phone when you tilt it and somehow it gets stuck in one orientation or the other (who knows maybe this one is just me, not seen any other backflips) if you set it back to just when you open/close it it's fine again though
- The desk clock can't be launched manually and is tricky to get to appear trying to get the phone in that perfect angle to display it
- I don't have a separate camera on me right now to show you the menu but to back up with sources:
http://www.pcworld.com/article/1910...n_atandt_not_the_full_android_experience.html
https://supportforums.motorola.com/message/121849
Don't buy this phone. Stay away from AT&T, stay away from Motorola (IMO or at least the motorola backflip).

This is pretty horrible.
I have two questions, though.
1) Can you take a screen cap of the Settings > Applications screen so we can see the lack of Unknown Sources option? That'd really help people see the validity of this issue.
2) I hope you have some kind of 30-day money-back guarantee when buying a handset from AT&T like Sprint offers. Otherwise, ouch =/

I haven't tried to install an apk from astro or anything, but i have pushed a few with ADB which seems to work fine. It kinda sucks, but I really hope that we can figure out root access soon! I don't care for blur, but I like android. Hopefully we don't have to wait to long. Here is an ADB guide http://forum.xda-developers.com/showthread.php?t=643866

I wonder if Apple suddenly took over AT&T because this kind of behaviour is more common to them

... It's not only AT&T who manages to confuse their customers about an OSS... Don't forget who decided to lock down an open software system boot-loader for everyone *cough*Motorola*cough*

Apple made them an offer they could not refuse!
nuff said

I spent some time with one yesterday.
Ouch, even my Fuze running eclair is faster.
They really broke this machine.
I am worried about other att phones!

My hope for an even somewhat open x10 on AT&T is starting to dwindle.

HushH said:
My hope for an even somewhat open x10 on AT&T is starting to dwindle.
Click to expand...
Click to collapse
mines as well. i hope they dont. i know its off topic but is there an officail release date for the x10 on att? i hear it may be april/may

Someone more familiar than I needs to figure out the proper java system call to enable unknown/untrusted sources and then post on this thread the proper at command to execute it via CLI. You wouldn't even need root to do this.

IConrad01 said:
Someone more familiar than I needs to figure out the proper java system call to enable unknown/untrusted sources and then post on this thread the proper at command to execute it via CLI. You wouldn't even need root to do this.
Click to expand...
Click to collapse
Assuming the software running on the Backflip is the same software they released the source to on opensource.motorola.com, there may be hope of that. I'll dig into it when I get time.

Wow. I am surprised that this was picked up by Gizmodo. Do we have anyone corroborating this? Doesn't this somehow violate Google's terms of service?

HushH said:
My hope for an even somewhat open x10 on AT&T is starting to dwindle.
Click to expand...
Click to collapse
Mine too! Just means to spend the couple extra hundred dollars and get an unlocked unbranded one.
I got the Backflip just because I am moving on from my jailbroken iPhone and I wanted something neat and shiny.
I can say that there is a lot of smack talk here, but give these guys a chance here to root the phone and get some things working on it.
It's been two days since the release and I can already say, that I like the phone a hell of a lot more today then I did on Sunday. I've been able to install untrusted sources using the Droid Explorer, a bit of a pain in the ass, but it's okay, considering that if I want Android, then this is the only way to go for now.
But I have faith in someone out there... Someone will figure this out.
I just hope it's within my 30 day return policy.
EDIT: I Installed "GDE" on my device and I am able to use the Google search widget... So that issue is sort of solved...

This may just be my unit but the A2DP doesn't work right, it starts playing music then begins to fast forward whatever you are watching or listening to. Did a hard reset, no luck. Looks like I already need a replacement lol.

Squeaky369 said:
EDIT: I Installed "GDE" on my device and I am able to use the Google search widget... So that issue is sort of solved...
Click to expand...
Click to collapse
Can you please explain how you got the google search widget working?

nutcake852 said:
Can you please explain how you got the google search widget working?
Click to expand...
Click to collapse
Eh; fail on my part. It's mostly a cosmetic fix. I didn't actually test it, but when you click on it, it changes to "Yahoo".
So my bad on that one.
God, I hate Yahoo. Ever since that stupid ass cowboy did that commercial, it's ate away at my soul...

I don't know why...
To think we were all worried about how Verizon was going to cripple android only to have ATT do it instead. At first I was amazed and then I realized that any android phone would have outshown their prized phone...oh well one more reason to love being on T-Mobile. ;-)

I played with a Backflip. My god it's a horrid phone. And yeah, Android is completely locked down, with no way to delete those AT&T apps and no installing off-Market Android Apps out of the box.
I was going to wait to see what AT&T was going to bring to the table, but I'm not holding my breath.
Btw, I noticed that AT&T trained to sell the Backflip pretty hard. Like, seriously, I was looking at phones today, and every other word out of the rep's mouth was that I should buy the Backflip. Thankfully I'm more informed than that. I walked out with an iPhone instead. (Don't grill me, I use a Touch Pro2, I just needed a good phone for my work line >_<)

Help i ****ed up my phone
So i just rooted my g1 to get the nexus one features to it and now all it is doing is foreclosing instead of going to the home screen if anyone can help can you please email me at [email protected] thank you

Xodium said:
I played with a Backflip. My god it's a horrid phone. And yeah, Android is completely locked down, with no way to delete those AT&T apps and no installing off-Market Android Apps out of the box.
I was going to wait to see what AT&T was going to bring to the table, but I'm not holding my breath.
Btw, I noticed that AT&T trained to sell the Backflip pretty hard. Like, seriously, I was looking at phones today, and every other word out of the rep's mouth was that I should buy the Backflip. Thankfully I'm more informed than that. I walked out with an iPhone instead. (Don't grill me, I use a Touch Pro2, I just needed a good phone for my work line >_<)
Click to expand...
Click to collapse
I really do think though that this is going to end up to be a decent phone.
I know I am a little pro for that comment, just because I bought one. But lets look at every phone that ever comes out. There is always some sort of challenge that we have to overcome.
And; with all the threads I've been reading about this; it looks like it was BOTH AT&T and Motorola that are to blame for locking this phone down. ATT cause they don't want us to install from anything but an "App Store" and Motorola because they don't want their devices used for what "there were not intended to be used for," is the wording I've seen floating around the internet.
But in all seriousness. I am coming from an iPhone 3GS which I had jailbroken. So I am coming from a phone that I had everything and anything on to this, and I am, overall, happy with it. Although it's only been 5 days, I can say I don't think I'll change my mind in the next 25 days.
But that's just my two-cents.

[Q] For those who just obtained a new captivate

I wanted to start a thread for those who just obtained a new captivate mostly for my own purposes. I am looking to obtain a list of action in the correct priority to improve the captivate experience. I know certain things need to be done in certain orders and it would be great if there was a running list with current links to resource those items.
For instance I am still running Stock 2.1 Update 1
I know I want to tether without contract additions. So much needs to happen before I can do so. I probably need to unlock the phone, update to the latest rev, remove the road blocks restricting unpaid tethering, etc.
Can anyone create a road map with links to accomplish this task... thank you from a long time member.

There are already guides out there if you search that will tell you how to do it. For 2.2 its as easy as rooting then deleting/freezing a .apk file
Sent from my SAMSUNG-SGH-I897 using XDA App

brokebackbear said:
I wanted to start a thread for those who just obtained a new captivate mostly for my own purposes. I am looking to obtain a list of action in the correct priority to improve the captivate experience. I know certain things need to be done in certain orders and it would be great if there was a running list with current links to resource those items.
For instance I am still running Stock 2.1 Update 1
I know I want to tether without contract additions. So much needs to happen before I can do so. I probably need to unlock the phone, update to the latest rev, remove the road blocks restricting unpaid tethering, etc.
Can anyone create a road map with links to accomplish this task... thank you from a long time member.
Click to expand...
Click to collapse
lol are u serious? Theres a ton of stuff that guides u on how to unlock ur phone. U can just go to youtube and fallow the directions on http://www.youtube.com/user/MobileTechVideos

japr2821 said:
lol are u serious? Theres a ton of stuff that guides u on how to unlock ur phone. U can just go to youtube and fallow the directions on http://www.youtube.com/user/MobileTechVideos
Click to expand...
Click to collapse
I am serious... this is a serious site. OF course there are videos out there but the correct order has not been published. For instance any idiot can upgrade to 2.2 but sadly unless they have been told to unlock first they cannot go back to 2.1. That's the kind of stuff I was talking about. You don't have to be mean. I have been here since 2008 and never been asked if I was serious.

unlock refers to it being locked to a carier. for permsions this is all linux/unix/terminal related and we use the terms root and super user. macs being a terminal type of interface also use these terms.
to be rooted means you have access to the root of the file system and to have superuser permissions. root of the file system is described by the character "/" this is similat to c:\ in windows but terminal doesn't have letter designations on drives.
to enable tethering the best way is to either update to 2.2 via kies, root and freeze an apk that will require you to have a tethering data plan. or the alternative is to install a rom for an i9000 or other phone such as the i9010 armani or the chinese i9088 or the t-mobile vibrant, though vibrant roms may cause battery drain, that has been my experience anyhow.

brokebackbear said:
I am serious... this is a serious site. OF course there are videos out there but the correct order has not been published. For instance any idiot can upgrade to 2.2 but sadly unless they have been told to unlock first they cannot go back to 2.1. That's the kind of stuff I was talking about. You don't have to be mean. I have been here since 2008 and never been asked if I was serious.
Click to expand...
Click to collapse
If u really mean recent captivate from at&t. they probably come woth froo loaded already. unless u got some left over stock from earliser batch.
Sent from my SGH-I897 using XDA App

tg9413 said:
If u really mean recent captivate from at&t. they probably come woth froo loaded already. unless u got some left over stock from earliser batch.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Wrong. Just got a Captivate from AT&T last month, because my old phone was pretty much unusable and I wanted something with more functionality. Still 2.1, and I attempted to upgrade to 2.2 following Samsung's instructions thoroughly and ended up with a bricked phone. Thankfully I was still in warranty since it was amazingly even less than 30 days that had passed, but still.
AT&T does not ship out the Captivate with 2.2, nor will they upgrade it for you. You get it 2.1, and have to upgrade it yourself. And if you happen to screw up somehow and actually hard brick your phone, to where it won't even turn on, they won't fix it. It's considered user error. Samsung will, but that's not the point here.

Delete....wrong thread.
But since I'm here......see below.

brokebackbear said:
I am serious... this is a serious site. OF course there are videos out there but the correct order has not been published. For instance any idiot can upgrade to 2.2 but sadly unless they have been told to unlock first they cannot go back to 2.1. That's the kind of stuff I was talking about. You don't have to be mean. I have been here since 2008 and never been asked if I was serious.
Click to expand...
Click to collapse
I have never unlocked my phone and have gone back to 2.1 literally a hundred times. Looks like some reading/learning is in order.
PS. Might want to go ahead and purchase/make your jig so you will have it when you need it.

Just got my captivate replaced at an att tech center yesterday and the new one came with froyo 2.2 preloaded.

The.Se7enth said:
Wrong. Just got a Captivate from AT&T last month, because my old phone was pretty much unusable and I wanted something with more functionality. Still 2.1, and I attempted to upgrade to 2.2 following Samsung's instructions thoroughly and ended up with a bricked phone. Thankfully I was still in warranty since it was amazingly even less than 30 days that had passed, but still.
AT&T does not ship out the Captivate with 2.2, nor will they upgrade it for you. You get it 2.1, and have to upgrade it yourself. And if you happen to screw up somehow and actually hard brick your phone, to where it won't even turn on, they won't fix it. It's considered user error. Samsung will, but that's not the point here.
Click to expand...
Click to collapse
Wrong... I just replaced my captivate a couple weeks ago and it came with 2.2. I have seen several people reporting for the last 2 months since froyo released that it was already on their phone. I remember one post stating they got their phone shipped 2 days after official release and it was already loaded
Sent from my GT-I9000 using XDA Premium App

Captivates ARE in fact shipping with 2.2 on them right now. I have several sitting at my desk right now.

Yeah, you need to read... Everyone started in your same shoes. But not everyone asked for step by step guidelines to do things to their phones. So, do your research, then if/when u get stuck or lost, and there are no threads out there to help, ask away!
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Here are the steps in order:
1. Root
2. Unlock
3. Flash ROM
4. Never look back

[Q] Questions about OTA rollouts???

As far as getting OTA updates, is there any difference between being on T-Mobile's phone network or on random wi-fi link? Does it make any difference if the sim card is in the phone or not?
I don't have reception at all at home so the phones are just on wifi and I often only spend a few hours a week on T-Mobile's network. So at that rate I may never get the OTA update. And lately my SIM card is in my spare rooted G2x which I've been using to try out ROMs.
Does anyone have any idea how phones are selected for updating? Random based on IMEI number? Phone number? SIM card? Date phone was purchased? Date the phone was manufactured? Does account type matter? Prepaid vs contract etc.?? The lack of info about this is infuriating. Same as the new market, weeks later, still no new market on my stock phone (not side loading anything on that phone).
The fact that Google has no direct support for Android at all and they are leaving support completely to grossly incompetent companies like LG and T-Mobile bodes very poorly in my estimation. Will this have me go to a locked down phone like iPhone or WM7 phones? No. But it leads me hoping they might open up WebOS more and get it on some better hardware.
Basically, is there anything I can do to influence the situation, or is it completely random? Does checking more often help, or will my phone only get the update once Google/LG/T-Mobile determine my phone will get it???

No one has any idea? Not even wild, inaccurate speculation??

I am interrested in knowing this as well! I spend most of the day on wifi calling either at work or at home...

I recently spoke to tech support he told me he would recommend updating thru the lg update tool because its a secure connection.
Sent from my LG-P999 using XDA App

I heard they use IMEIs, but I don't think the IMEIs are necessarily in order of oldest to newest. One of my buddies who bought his nexus one from google a couple months after I did would always get OTAs before I did.
And we both got OTAs over wifi. I wouldn't know if your sim card needs to be in there, but I would definitely leave it in and just run the *#*#checkin#*#* command just in case.
But nonetheless, to anybody:
Please use alogcat while downloading the OTA.
Once done, just upload the whole logcat so that we can find the URL for the OTA.

Ha! Strangely, I got my OTA GB today. While on cellular, not wifi. Go figure.
Still waitin' on the new market......
Sorry, I wish I had known about the logcat thing. I may flash stock 2.2 onto my spare rooted g2x and wait to see when it gets the OTA, I want nothing to do with the LG updater app, but I might loose patience, we'll see....
Oh, and the *#*#checkin#*#* command??? Has this been tested to work on the G2x? Is that regarded as useful on Android phones in general? Or certain brands, like just HTCs? Search isn't showing too much info on that.

Ha! Strangely, I got my OTA GB today. While on cellular, not wifi. Go figure.
Still waitin' on the new market......
Sorry, I wish I had known about the logcat thing. I may flash stock 2.2 onto my spare rooted g2x and wait to see when it gets the OTA, I want nothing to do with the LG updater app, but I might loose patience, we'll see....
Oh, and the *#*#checkin#*#* command??? Has this been tested to work on the G2x? Is that regarded as useful on Android phones in general? Or certain brands, like just HTCs? Search isn't showing too much info on that.

[Q] voice search bug but no OTA update yet

I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.

3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium

you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062

hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?

Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.

The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box

ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.

like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.

hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S

3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).

ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.

Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?

ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.

3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.

I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.

I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)

ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny

[Q] Anyone experience earpiece issue?

On my skyrocket from AT&T I was having an issue with the battery indicator getting stuck at 100%.
I updated the phone to the latest OTA update, no root or anything on this phone, all completely stock.
After update phone info is as follows:
Model Number: SAMSUNG-SGH-I727
Android Version: 2.3.6
Baseband Version: I727UCLA3
Kernel Version: 2.6.35.11
Build Number: GINGERBREAD.UCLA3
After I did the update the battery indicator has not come back (awesome right?, not so fast.)
Now I have an issue with call quality, my best attempt at describing it is like the ear piece sounds blown out, it kind of has a vibrate when people talk, Its not just one persons phone either, its any call I get/place.
I'm not sure if I should try a factory reset, revert back to 2.3.5?, Go to AT&T for a new one.
If anyone has had this issue and knows how to fix it please post. I apologize ahead of time if this is already posted somewhere, I looked for a few hours on google and couldn't find it anywhere. Also even if you don't know how to fix it, could you please post if your having the same issue so I know I'm not alone and have some ammo if I do have to go to AT&T.

Visit AT&T Store
Of course I'm 4 days outside my 30 day trial period so I would have to get a replacement mailed to me if I can't get it to work.
Lady I spoke with there was very nice (as always) but didn't have any idea what to do (as always) and advised I try and factory reset it. What the hell, mine as well.
Also got her to tell me that if I root and custom rom it and it still dosn't work I can still RMA it. So she went against what all their documentation says so now I can do what I want
Figure ill factory reset first, if that dosn't work I'll ODIN it back to the original 2.3.5 if possible.
Ill keep updating this thread though incase anyone else has a similar issue.

albeemichael said:
Of course I'm 4 days outside my 30 day trial period so I would have to get a replacement mailed to me if I can't get it to work.
Lady I spoke with there was very nice (as always) but didn't have any idea what to do (as always) and advised I try and factory reset it. What the hell, mine as well.
Also got her to tell me that if I root and custom rom it and it still dosn't work I can still RMA it. So she went against what all their documentation says so now I can do what I want
Figure ill factory reset first, if that dosn't work I'll ODIN it back to the original 2.3.5 if possible.
Ill keep updating this thread though incase anyone else has a similar issue.
Click to expand...
Click to collapse
Haha, just because she said that doesn't mean anything. Read the contract, that trumps what some lady says. Anyways, you can flash back to stock and warranty it, so it doesn't matter what anyone says

Absolutely Right
xcrazydx said:
Haha, just because she said that doesn't mean anything. Read the contract, that trumps what some lady says. Anyways, you can flash back to stock and warranty it, so it doesn't matter what anyone says
Click to expand...
Click to collapse
As the title says you absolutely correct. Lady probably didn't have a clue lol.
I called their warranty support line and am going to drive to their wallingford exchange place.
I was talking with my father before I called and figured if I went in and said get a manager, and told him/her if I don't have a new phone in my hand in 10 minutes, your losing a customer in 10 minutes, I bet I would get my phone
Regardless I'm getting a replacement, I did try the factory reset, didn't work. Also tried downgrading the device to 2.3.5 stock, and this also did not work.
Think its hardware, the static is only on the ear piece. Speaker phone, head phones, and bluetooth do not have the issue so I think its a odd coincidence

To anyone that may have been checking on this, it seems I got a rare case, there was actually a hardware problem on my device. Just a coincidence that I noticed it right after an update, I took it to the Customer Service place AT&T has in Wallingford, CT and the lady tried to re-flash the phone (what she said was standard procedure, she HAS to with every issue.) This didn't work so she gave me a new one.
All in all, only bad part of the experience was that it happened at all. New phone is working great.

Glad tohear that you got this taken care of.
Sent from my SAMSUNG-SGH-I727 using xda premium