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
It seems like almost every other variant of the S5 has now been updated to 4.4.4. Verizon has actually even updated their 4.4.4 with a newer patch. So, what's the hold up with Sprint? I love locking my phone with the finger print scanner, but it takes several swipes to unlock it most of the time. I understand that's fixed. Bluetooth audio is also barely usable as it's so choppy. I hear that's also been fixed. What's taking them so long to release the update?
Every carrier is diffrent if you notice theres things in the Verizon update that we have now. Ive only seen the Verizon update for the s5 and international. Im actually glad there taking there time maybe theyll get it right on the first go maybe theres a reason Verizon already got a patched update could be because they rushed it out.... I see alot of people complaining that they have to wait for a update and then when the update hits they complain that it has bugs.
Amen, Evo.
Why does this matter? 4.4.4 is a minor update with no new must have features that I am aware of. If I was a developer I would skip it. Android L will be out soon enough.
http://www.gsmarena.com/galaxy_s5_and_note_4_might_get_android_l_by_early_december-news-9691.php
socos25 said:
Why does this matter? 4.4.4 is a minor update with no new must have features that I am aware of. If I was a developer I would skip it. Android L will be out soon enough.
http://www.gsmarena.com/galaxy_s5_and_note_4_might_get_android_l_by_early_december-news-9691.php
Click to expand...
Click to collapse
I think I mentioned why it matters to me. It might not to others. I would like to have a better, more usable finger print scanner and non-skipping music through bluetooth for my car, speaker and earphones.
I don't care how that's delivered, but it looks like the new update fixes those issues.
This is not a question that can be answered here. It is like asking for an ETA.
Only Sprint technicians in charge of OTAs would even have an inkling of an idea when an OTA may be coming.
The best thread to keep an eye on and discuss changes is this one
Thanks
FNSM
I am in the US on an unlocked S7 G930U.
Earlier this week I received notice of a Software Update.
I am always hesitant to install these updates until I know what they are and see what people are saying about their performance.
I havent seen anything about this here (am I missing it somewhere) although on GSMArena there is a scary sounding thread with people installing a recent update and having major battery issues.
Is there anyway to see what this update is before it gets installed? Any ideas? Thanks.
BTW - the update is ~452MB.
lirong said:
I am in the US on an unlocked S7 G930U.
Earlier this week I received notice of a Software Update.
I am always hesitant to install these updates until I know what they are and see what people are saying about their performance.
I havent seen anything about this here (am I missing it somewhere) although on GSMArena there is a scary sounding thread with people installing a recent update and having major battery issues.
Is there anyway to see what this update is before it gets installed? Any ideas? Thanks.
BTW - the update is ~452MB.
Click to expand...
Click to collapse
I'm kind of new here, but after reading up on the Samsung support forums apparently G930U will only be receiving quarterly security updates so this update is all of the regular updates the carrier versions have received since September rolled up into 1 large package. It's still 6.0.1, and so far, I haven't seen any adverse effects (although I'm not rooted, so no clue if it effects anything along the lines of the boot loader) Also, during my internet search on what this update was, I came across this site that lists out the firmware (and Android level) of every release for a Samsung product, which confirmed not the nougat update. - can't make a real link since I'm new to posting on XDA, so search Google for "live-samsung updates"
Hope that helps!
lirong said:
I am in the US on an unlocked S7 G930U.
Earlier this week I received notice of a Software Update.
I am always hesitant to install these updates until I know what they are and see what people are saying about their performance.
I havent seen anything about this here (am I missing it somewhere) although on GSMArena there is a scary sounding thread with people installing a recent update and having major battery issues.
Is there anyway to see what this update is before it gets installed? Any ideas? Thanks.
BTW - the update is ~452MB.
Click to expand...
Click to collapse
I updated my G930U and have had no issues. Took it off the charger this morning at 8am, it's now nearly 1pm and battery is at 97%. Obviously I haven't used it much but there's certainly no unusual standby battery issue so far.
Today I saw that no matter the theme of the phone the update interface in settings turn white, all text disappeared and the only text showing now is "YOUR SYSTEM IS UP TO DATE". No more version, no more last check, etc. Is this the sign the phone was disconnected from the Xiaomi servers? I thought this was supposed to be the last month of updates.
Nothing changed in my update interface in settings, I'm on june 2021 security patch, dark theme, and I can still check for updates.
But indeed I doubt that we still have updates (maybe one last...)
Mellow971 said:
Nothing changed in my update interface in settings, I'm on june 2021 security patch, dark theme, and I can still check for updates.
But indeed I doubt that we still have updates (maybe one last...)
Click to expand...
Click to collapse
This is what happened to me... can't be an isolated case, that's why I'm asking.
TeoXSD said:
This is what happened to me... can't be an isolated case, that's why I'm asking.
Click to expand...
Click to collapse
That's exactly what mine looks like although what it means regarding any updates is anyone's guess. As it happens my screen has started to separate just this week with long streaks up both sides. It's not affected performance yet (and may not do) but along with the lack of updates from now on I took the opportunity to order a Poco X3 Pro 8/256MB. Perhaps Outlook will decide to start working again for me
The last "performance" update was upgrade to android 10 and maybe few following, all others was security patches from google! No one cares about this model at list one year, wake up guys! Thanks god we have a realy big community, and still rolling out new customs for this model.
Hi All.
I'm on May 1 update now. Recently mobile data stopped working from time to time and cellular signal doesn't function on incoming calls and SMS when SIM is in slot 1.
Seems more like a hardware issue to me, but did you experience anything like that with your Mi A2 Lite?
guess its time to move to a stable custom rom, maybe with dt2w
Maybe But if it is a hardware fault the rom won't matter.
its not hardware, we had it and they removed it with i cant remember wich update
https://www.androidpolice.com/google-delays-august-pixel-patch/
This is really infuriating especially considering that Samsung is rolling out the August updates to their phones. I really wonder at times if the Pixel software team is a couple of folks kept in a back room. It really seems that as time goes on Google cares less and less about providing timely bug free updates to the Pixel line.
There were several times since the P6/P6 Pro release that Google delayed those updates, but it's very rare Google delays the entire line of updates. Definitely frustrating!
I wonder if the reports of p6a fingerprint sensor allowing for non registered fingers is the root cause to pull the updates so close to release.
bartolo5 said:
I wonder if the reports of p6a fingerprint sensor allowing for non registered fingers is the root cause to pull the updates so close to release.
Click to expand...
Click to collapse
No. If there was a specific issue with the P6a software update, they simply would have delayed that image from being released. They still would have released the update for the rest of the Pixel lineup. As I mentioned above, this has happened with many of the initial P6/P6 Pro updates where Google delayed those updates due to bugs, but released the rest of the Pixel updates on time.
EDIT - Perhaps you are speaking of the "missing" July update. I initially though you where speaking about the delayed Aug updates. However I don't think Google "pulled" a July update - I simply don't think it existed. Google isn't going to waste the time and resources in creating a monthly update for a phone that isn't released yet. I'm assuming Google was planning a regular Aug release which would include all the needed updates to the P6a which should have been released just days after the phone was released.
greatgoogly said:
https://www.androidpolice.com/google-delays-august-pixel-patch/
This is really infuriating especially considering that Samsung is rolling out the August updates to their phones. I really wonder at times if the Pixel software team is a couple of folks kept in a back room. It really seems that as time goes on Google cares less and less about providing timely bug free updates to the Pixel line.
Click to expand...
Click to collapse
Updates are generally delayed because they found an issue that they didn't want to push to the general public.
Be patient. The update will come. Would you rather have a good patch that's a little late, or a broken update on time?
Of course, some people will complain either way...