Related
EDIT: FALSE ALARM, AT&T thinks I need an update.
I looked around the forum to see if I could find something about this and couldn't, maybe I missed it.
I have Cog 2.3B6 (Froyo), and I just got a text message from at&t saying:
AT&T is providing a free update for your phone. When asked to install the update, please select OK. Thank You.
What update could this possibly be, official Froyo?
Edit: Also when I was reading my message, my phone was also trying to connect to DM, whatever that means. Not sure if it's related or not.
Probably just jh7.
Sent from my Captivate
any update?
didn't think you would get a notice rooted on custom rom.
Ahh. You got my hopes up...
Just checked.. nada. Running Jh7 stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Lots of people with custom roms get that. AT&T's notification sytem sees that you are not on what they consider to be the latest version.
Ahh ok, thought it might be a false alarm. Thanks.
OP can you edit your post title so everyone doesn't come here and flame you... There should be some kind of MOD editing of these type of update posts that turn out to be false alarms. It think there are an average of 4 or 5 of these a day.
tahoeski said:
OP can you edit your post title so everyone doesn't come here and flame you... There should be some kind of MOD editing of these type of update posts that turn out to be false alarms. It think there are an average of 4 or 5 of these a day.
Click to expand...
Click to collapse
For sure. For the last time, most developers have it on good notice that this won't happen until Q1 2011.
If it drops before that, I'll eat my words but until then stop it.
Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App
Yea I got a text running perception 5. Not sure its froyo or a really late text for jh7.
I've been getting them for the last few days, though I'm not willing to flash to find out lol....
I got it shortly after flashing to cognition 2.3b6 - checked for new OTA updates and didn't get anything.
Just tried and failed to connect to server.. though it's probaly nothing. Been a lot of posts about people getting texts to update (I haven't gotten one, I'm running stock JH7). I think it's just AT&T trying to get everyone to update to JH7.
From androidforums.com:
"This has been happening for a while now. People who are running anything other than Samsung/AT&T firmware have been getting these notices."
Stock
JimmehDean said:
Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope. Stock.
1. AT&T doesn't know what firmware you are running. They are STILL sending out general update notifications to remind people to update to JH7.
2. There are two other threads in the forum, on the front page discussing the same topic...LOL. Come on guys.
For whatever it's worth, I spoke with three AT&T techs today, from common answerer, all to UPPER LEVEL WIRELESS TECH, and the answers I got from all three, screwed my thinking, which at times, AT&T does well. The OTA to side-load they been speaking of, IS NOT A SOFTWARE UPDATE, as I thought it had to be, but online instructions, on how to make am adjustment, Menu, then Settings, to stop BLOCKING the install of NON MARKET APPS, like from Amazon. I thought the OTA, was a software 'patch' that would fix the blocking of apps not from the Market, but they all told me, that the OTA, was really a set of steps, that showed you how to make the MANUAL ADJUSTMENTS, on my Captivate. Maybe I'm the only one feeling like an idiot over this, but that is how I was left feeling. They sent not one, but two different text mess., that for some reason, didn't do a thing, so the upper level tech, tried walking me through the adjustment, his own self, but he flat failed to tell me how. He finally suggested, that since it was Amazon's appstore app I was trying to install, and my Captivate still was BLOCKING the install, to ask AMAZON for help, in case THEY KNOW how to make the adjustments on the Captivate, or better, to ask SAMSUNG, since it's their phone. The guy was nice..., but why do I feel shafted for paying outrageous premiums for service from AT&T, but when I ask for help, I get shoved along to someone else, for them to help me?
Has anyone heard, that the OTA, is NOT SOFTWARE, but actually instructions, to make in your phones settings? If anyone could give a rational explanation of this to me, I'd appreciate it. My AT&T Samsung Captivate, is a great phone, to me, but AT&T, leaves a lot to be desired. Any suggestions?
Please don't hijack threads.
Anyways if it is instructions then they will need to push out an ota to even enable the option. They removed the option to prevent people from enabling it to begin with.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
AT&T updates
JimmehDean said:
Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Last night my wife's phone completely hung. Had to use 3-button combo to get into recovery and reboot. After reboot, Device Management was running endlessly. Tried to kill it but it wouldn't stop. Tried to use TIBU to freeze it but TIBU wiuldn't open. Finally killed it by clearing Device Management data. Went into TIBU again and froze it. Unbelievable. Her phone is stock 2.2 but rooted. 2 hours later, I noticed on my phone that Device Management was running (notification bar). Went through the same sequence to kill it and freeze it. I will never defrost this!!
On my stock 2.2 not rooted cappy it was enabled just by turning the phone off and back on a couple of days ago.
Sent from my SAMSUNG-SGH-I897 using XDA App
ffman2152 said:
For whatever it's worth, I spoke with three AT&T techs today, from common answerer, all to UPPER LEVEL WIRELESS TECH, and the answers I got from all three, screwed my thinking, which at times, AT&T does well. The OTA to side-load they been speaking of, IS NOT A SOFTWARE UPDATE, as I thought it had to be, but online instructions, on how to make am adjustment, Menu, then Settings, to stop BLOCKING the install of NON MARKET APPS, like from Amazon. I thought the OTA, was a software 'patch' that would fix the blocking of apps not from the Market, but they all told me, that the OTA, was really a set of steps, that showed you how to make the MANUAL ADJUSTMENTS, on my Captivate. Maybe I'm the only one feeling like an idiot over this, but that is how I was left feeling. They sent not one, but two different text mess., that for some reason, didn't do a thing, so the upper level tech, tried walking me through the adjustment, his own self, but he flat failed to tell me how. He finally suggested, that since it was Amazon's appstore app I was trying to install, and my Captivate still was BLOCKING the install, to ask AMAZON for help, in case THEY KNOW how to make the adjustments on the Captivate, or better, to ask SAMSUNG, since it's their phone. The guy was nice..., but why do I feel shafted for paying outrageous premiums for service from AT&T, but when I ask for help, I get shoved along to someone else, for them to help me?
Has anyone heard, that the OTA, is NOT SOFTWARE, but actually instructions, to make in your phones settings? If anyone could give a rational explanation of this to me, I'd appreciate it. My AT&T Samsung Captivate, is a great phone, to me, but AT&T, leaves a lot to be desired. Any suggestions?
Click to expand...
Click to collapse
What is with all of the commas? Load a rom and don't worry about any ota from AT&T!
This is my Captivate. There are many like it but this one is mine
no problem here rogers Canada ftw side loading enabled from the beginning. and as for the messages if you want them to stop just block them. and chances are if your on this site you have sideloading anyways
http://www.engadget.com/2010/12/31/android-still-has-horrible-text-messaging-bugs-thatll-get-you-f/
Is this really a widespread problem, or is it more Engadget anti-Android propaganda?
Not sure but I haven't experienced it in almost a year of using several android devices.
I use Handcent, so I have no idea what they're talking about.
Sent from my Nexus S using Tapatalk
Read the source links.
For the record, I love android. I hate all the anti-android crap going around. But I have experienced this before. One time upon booting up, my contacts were all mixed up with the wrong numbers. It was so weird. My friend became my dads name on there and another friend became my cousins whom I never texted. So when they texted me I saw the names and was like wtf? How do they know about (whatever we were chatting about earlier). Took another reboot and everything was fine. I also experienced the phone clicking on the wrong thread that I pressed, that definitely happens. I've learned to double check who Im texting.
Is this fixed by using a different SMS app then? Apparently it happens with e-mails, too, but only with the default e-mail app.
I have been using an HD2, that dual boots WM 6.5 and Android 2.2 Froyo, never had this problem.
My daughter uses a Behold 2 and sends and receives over 16000 text messages per month, and never a problem like this.
I think it's more hate against Android, since it is starting to get a strong hold of the smartphone market.
I'm also sure it's a lot of user error too.
Google just updated this to critical, so I'm guessing it'll be patched pretty soon.
It happens to me at least twice a week. I actually switched to handcent it was so bad. Thankfully I never had anything truly embarrassing go to the wrong person, but I have had some confusing moment...The worst was when I carried out a long conversations with the wrong person... The problem happens when you click on the new message item in the notification menu without actually opening it up through the messaging app. You see the correct reply thread, and it is only when you press send that you realize it sent to the wrong person. This is very real, but I used to think it was just my phone.
lmao. This is just amusing.
The ONLY time I ever got the bug was when I received a new message, I used the drop down menu bar to view the message, and this was on a beta froyo build. Any time I went through the regular messaging app, everything was fine. Last I read in a forum long ago burried, only time the bug happened was when you used the drop down...
I've used Android since the G1 was released and don't remember ever experiencing this issue. But if it is an issue, then it needs media attention to get Google to fix it as quick as possible. Although, the problem is getting the fix out, since you know, all these carriers and manufacturers take forever to get an OTA out.
Google said:
Hi all,
I want to let everyone know that we are actively investigating this issue, and we hope to have an update soon. Obviously, this is a very difficult to reproduce bug.
Rather than replying "me too", you can star this issue to follow it. Just saying "me too" just obscures the useful information in this bug, and makes it harder to fix. Of course, if you have useful information to add to the bug, such as a system dump or an insightful analysis of the code, feel free to update the bug with your observations.
Click to expand...
Click to collapse
So they are now investigating this. I'll be using Handcent on my DHD until they sort it.
tooter1 said:
I have been using an HD2, that dual boots WM 6.5 and Android 2.2 Froyo, never had this problem.
My daughter uses a Behold 2 and sends and receives over 16000 text messages per month, and never a problem like this.
I think it's more hate against Android, since it is starting to get a strong hold of the smartphone market.
I'm also sure it's a lot of user error too.
Click to expand...
Click to collapse
16,000? I'm sure most networks in the UK have a 3,000 FUP
Anyway, I haven't experienced this issue in the 18 months I've been using Android
LooieENG said:
16,000? I'm sure most networks in the UK have a 3,000 FUP
Anyway, I haven't experienced this issue in the 18 months I've been using Android
Click to expand...
Click to collapse
I can believe 16,000. My 17 year old sister has about 10,000 a month. Unlimited texting, ftw.
I've been using Android since the release of the HTC Dream in Canada and I've never ever ever ran into this problem, and most of the ROMs I've ran have been beta or experimental. I'm thinking they're blowing it out of proportion.
TheBiles said:
I can believe 16,000. My 17 year old sister has about 10,000 a month. Unlimited texting, ftw.
Click to expand...
Click to collapse
When we were on Verizon, one month it was up to 39,000. I was floored. That is when I was like thank goodness for.....Unlimited Texting FTW!
Still no problems like this.
I've never had this problem and Goggle has made a press release and said they are having a hard time replicating it. I think that there could be an error that happens once in a blue moon, but I think most of the time it's just user error.
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic! http://mobilehighway.blogspot.com/
TheBiles said:
I can believe 16,000. My 17 year old sister has about 10,000 a month. Unlimited texting, ftw.
Click to expand...
Click to collapse
Oh yeah, I believe it. I'm just curious as to how their fingers haven't worn to the bone yet?
Googles claiming they can't reproduce this internally and they've only upped it's status cause of bad publicity. That's what androidguys claim ...
Sent from my Nexus One using XDA App
Yeah sometimes when I get a message I click on the thing in the drop down menu and it takes me to another thread, but I'm pretty sure the point of clicking that button is just for it to get you to the messaging app. Also sometimes I go to the messaging app and click the top thread and it takes me to a different thread. So this bug is true at times.
EDIT: Yes I know that this has been a long standing issue...but I never heard of it until it happened to me!!! So no need to come in and comment like 4 or 5 others felt the need to do with "lol this is old news u r teh dumbz hurr" I just wanted to bring this up to any new captivate owners like myself :]
If for some reason you have a hankering for some stock 2.1 from your captivate like I did for whatever random reason tonight......if you see an an OTA (Over The Air) Update for your captivate....DO NOT DO IT!!!!!! I say this because I did this tonight thinking that MAYBE this was some form of a 2.2 silent update push..or hell just some bugfixes would have been nice...so i went ahead and downloaded it, it prompted for a restart so it could flash it......and when it attempted to flash...it got about 50% and failed! Well at this point im thinking...awesome...ATT at its finest. So it said it was going to reboot back to android, I waited patiently...waited.....it hot about 3 minutes with phone in hand and screen off when i feel 2 *buzz* buzz* ! I think to myself HOORAY! its okay ....well i was wrong...that was my Captivates last words so to speak. I have tried plain powering on the phone....trying to go into recovery, trying to go into download mode even using a JIG to get back into download mode.....nothing the screen is blank completely, seems as if its not even getting power. :\ I am now the sad owner of a Captivate shaped door stop /facedesk .....Thankfully i yelled at the ATT people on the phone tonight enough to get a replacement phone lol! I am greatfull for this and felt as if i should pass this along to you guys until this gets sorted out. And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
bradleyG said:
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
this wasnt a post about me getting my hopes up for a 2.2 update lol. This was a warning to those who dont about that fail update thats messing up a ton of phones. ;D
blackberry,iphone captivate, whatever. i have learned NEVER EVER do OTA update download it from phone authors site or whatever no matter what phone it is OTA is spelled BRICK....
I didn't received any ota from att but last year I forced update my phone and it works fine with me though without any issue. I think its the same ota update but I manually force to update my phone lol
Sent from my SAMSUNG-SGH-I897 using XDA App
leo5111 said:
blackberry,iphone captivate, whatever. i have learned NEVER EVER do OTA update download it from phone authors site or whatever no matter what phone it is OTA is spelled BRICK....
Click to expand...
Click to collapse
I'm of the assumption that a OTA bricks less than 0.1% of the devices that attempt an update. Granted that may be a large number if the number of devices are large..but not much of a chance to brick in the big picture
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
HaiKaiDo said:
And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
Click to expand...
Click to collapse
That thread started in September, that's ancient in tech years.
bradleyG said:
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
+1 Still betting on St. Patty's Day release, office pool ya know.
Razzman said:
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
Click to expand...
Click to collapse
+100 Mine got the OTA fine and it was even rooted on edge service. Meh, who can tell why some did brick and others didn't. For sure I'll never do another OTA again. I love my 1007 build too much to return it.
HaiKaiDo said:
If for some reason you have a hankering for some stock 2.1 from your captivate like I did for whatever random reason tonight......if you see an an OTA (Over The Air) Update for your captivate....DO NOT DO IT!!!!!! I say this because I did this tonight thinking that MAYBE this was some form of a 2.2 silent update push..or hell just some bugfixes would have been nice...so i went ahead and downloaded it, it prompted for a restart so it could flash it......and when it attempted to flash...it got about 50% and failed! Well at this point im thinking...awesome...ATT at its finest. So it said it was going to reboot back to android, I waited patiently...waited.....it hot about 3 minutes with phone in hand and screen off when i feel 2 *buzz* buzz* ! I think to myself HOORAY! its okay ....well i was wrong...that was my Captivates last words so to speak. I have tried plain powering on the phone....trying to go into recovery, trying to go into download mode even using a JIG to get back into download mode.....nothing the screen is blank completely, seems as if its not even getting power. :\ I am now the sad owner of a Captivate shaped door stop /facedesk .....Thankfully i yelled at the ATT people on the phone tonight enough to get a replacement phone lol! I am greatfull for this and felt as if i should pass this along to you guys until this gets sorted out. And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
Click to expand...
Click to collapse
August called it wants its omg failed update back
Sent from my SGH-I897 using XDA App
Razzman said:
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
Click to expand...
Click to collapse
Yup... This, but then my phone was new and unmodded at the time.
Thx for the info
viperrepiv said:
Thx for the info
Click to expand...
Click to collapse
No problem
I know its easy to flame. But we were all new once.
smokestack76 said:
I know its easy to flame. But we were all new once.
Click to expand...
Click to collapse
Join Date : March 2010
New
cappysw10 said:
Join Date : March 2010
New
Click to expand...
Click to collapse
July 2010 for you. You are new as well
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