Related
I was one of the folks who got pushed the 20110509 build (came down this morning). Now, I have no dock at all. If I try to boot the machine with the dock attached, it stays stuck on the boot screen for minutes. If I boot without it and attach it, nothing happens for about a minute, then I get a battery icon with a question mark on it in the info window...that is it. It still is not registered with the system.
What...the...hell?
Were you rooted when you tried applying the new OTA ?
Negative. I've not rooted yet.
Sounds like you need to factory reset.
US version?
Yes, US version. Stuntdouble, is there no way to roll back an update? As in, reapply an older firmware file (20110423) that I have?
meatlocker said:
Yes, US version. Stuntdouble, is there no way to roll back an update? As in, reapply an older firmware file (20110423) that I have?
Click to expand...
Click to collapse
No I don't think so. Unless you root and re-flash with one of the roms from the dev section. Although now I've said that I'm not sure you can root from this new version yet.
Is it at least worth trying grabbing the correct downloadable firmware file from the Asus website and seeing if it will apply it ?
Yeah but only if a factory reset doesnt restore the unit to working with the dock first. I'm not a betting man but I reckon that will fix it.
Unfortunately, it didn't...I still have the same firmware (20110509) that I did before the wipe. I think the problem lies there, so I am going to need to figure out how to flash a prior firmware.
Thanks for the assistance thus far, guys.
I didnt expect it to wipe the firmware update but I did expect it to fix the connection problem. Good job I didnt bet. Anyways sorry you're having the problem. Probably a good idea to chat with those clever folks in the dev section to get it sorted though.
Thanks for the help. I was able to roll back the firmware of the device, but the dock issue remains. I am assuming that the dock itself has some kind of firmware, and that it is what got hosed.
Seams ro be plenty of people that are happy with the beta firmware. Try it one more time
Looks like the firmware push was a one-shot deal. I am not getting it offered to me again when I check for updates. As far as the dock goes, the power light is not even coming on when plugged in anymore. Friggin' weird.
meatlocker said:
Looks like the firmware push was a one-shot deal. I am not getting it offered to me again when I check for updates. As far as the dock goes, the power light is not even coming on when plugged in anymore. Friggin' weird.
Click to expand...
Click to collapse
Makes me scared to do the update that I requested from him. Looks like you were the one unlucky one of the batch according to the other dock update thread. Sucks!
This was a BETA firmware update so yeah once you download it it thats it.
Theres no real reason to discus it here any further, you need to contact the Asus dev thats been working with us on this and he'll work with you to get your dock working again. They did this beta release to make sure it worked before going with a full release. You signed up for a beta unverified release, that means there could be issues.
As you can see in the topics, most of us have had no issues. so just go talk to the asus dev and i'm sure he'll work with you to repair everything.
Already PM'd him. Will update with a response.
meatlocker said:
Already PM'd him. Will update with a response.
Click to expand...
Click to collapse
the fact he plugging it in has no light on sounds to me the dock is broken. factory reset wont help because that resets the tablet only. seem like a particular case here tho. i bet if you try a different dock itll work just fine. best of luck you find a fix soon.
mine installed the beta tablet firmware, then as soon as it booted it updated the dock firmware
did yours update the dock firmware on next reboot?
also... this may sound dumb, but does the dock have any battery life? Unplug your tablet from it, and plug the charger into it. See if the LED lights turn on...
No, it didn't. I got no notification at all about the dock getting updated (or needing to be updated). They were connected when I got the update, the unit restarted, and no more dock. If I try to restart with the dock in place, it just hangs on the second Asus boot logo. 2 seconds after I undock, I end up on the login screen.
I've spoken to Asus this morning, run through the normal wipe steps, and now waiting on a senior tech call. I doubt there is much that they can do, unless there is a magic key combo or other backdoor to refire the dock. It looks like I'm going to be RMA'ing back to NewEgg.
It's interesting that everyone else who has done this update has said that there is a 'part 2' to the update, which updates the dock. So the dock itself has firmware, this pretty much confirms.
I've done some looking on here and a bunch of other forums but I've not found anything. If I've overlooked something please let me know. I recently got the notice for the 8.4.4.11 firmware update for the TF and, for a number of reasons it failed. Now I can't get my TF to see that an update is available. I've manually checked numerous times and rebooted countless times to no avail. I've scoured the net looking for the US 8.4.4.11 package to download to install manually but I've not been able to find anything. The only thing listed on the Asus website is 8.4.4.5. Can someone out there provide a link to the US update? Thanks.
Look in the "Just got an OTA update" thread and you'll find the update.
martijua said:
Look in the "Just got an OTA update" thread and you'll find the update.
Click to expand...
Click to collapse
This looks to be what I was looking for. I apologize that I missed it in the first place. I appreciate the help. Cheers!
Interesting incident today. TF off and docked,but not closed measuring battery drain. calendar tiggered alert and TF woke up,but did not recognize dock and dock unresponsive.
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
I have a wifi only Xoom and it is Rooted. My question to you is, since it is rooted I obviously cannot be updated via OTA, it keeps showing up that I need to update. I cannot turn off automatic update when I go to about then update. Its really no big deal tbh, but it is really flipping annoying and just keeps coming back...
I would really appreciate some feed back and hope someone knows how to fix my problem. Thanks XDA!!!
Sent from my Xoom using xda premium
Assuming you have CWM installed, you could follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1575393
Install the update via CWM and get to 4.0.4 that way...... Ok, its not inhibiting the update notification per-se, but gets you on the latest stock build and keeps your rooted status.....
I would also suggest you check out voodoo root saver on the market. Its supposed to let your root survive an ota update.
Nickitt said:
I have a wifi only Xoom and it is Rooted. My question to you is, since it is rooted I obviously cannot be updated via OTA, it keeps showing up that I need to update. I cannot turn off automatic update when I go to about then update. Its really no big deal tbh, but it is really flipping annoying and just keeps coming back...
I would really appreciate some feed back and hope someone knows how to fix my problem. Thanks XDA!!!
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Make sure you read the "General" and "Android Dev" sections also - don't just ask a question in "Q&A". As stated in post #2, there is an existing (though only about 1 day old) solution - and it worked quite well for me.
Good luck.
willysp said:
Make sure you read the "General" and "Android Dev" sections also - don't just ask a question in "Q&A". As stated in post #2, there is an existing (though only about 1 day old) solution - and it worked quite well for me.
Good luck.
Click to expand...
Click to collapse
Well mister, how about you go ahead and post that sweet little HTML so I may click on it and square this away eh?
Or, it would be amazing if someone can just simply tell me which process to freeze. Cannot find a damn process with the word "update" in it to freeze.
IDGAF about a damn update, like I said, I am CONTENT with everything I have on my XOOM right now. Simply need to find the "process name" to freeze..
Sorry to be short, but I am pissed off, aggravated and personally am about to throw this in the Hudson river.
Nickitt said:
Well mister, how about you go ahead and post that sweet little HTML so I may click on it and square this away eh?
Or, it would be amazing if someone can just simply tell me which process to freeze. Cannot find a damn process with the word "update" in it to freeze.
IDGAF about a damn update, like I said, I am CONTENT with everything I have on my XOOM right now. Simply need to find the "process name" to freeze..
Sorry to be short, but I am pissed off, aggravated and personally am about to throw this in the Hudson river.
Click to expand...
Click to collapse
I thought from your first post that you wanted to be able to update and stay rooted. I referenced the "sweet HTML" already in post #2 as a way to update and stay rooted.
Hi guys, I know this issue has been reported here a bit. It wasn't bothering me too much but recently it seems to have gotten a lot worse. My pixel seems to drop connection pretty regularly and then take a good while to reconnect. I find myself reseting my internet settings a good bit and then it behaves itself for a while before dropping again.
I'm still on October build, but I've gotten a fresh sim card, updated sim manager and I have done the force lte trick but nothings really helped. I spend a lot of my time seeing the exclamation mark on my coverage icons and messing around with settings trying to get it to reconnect.
I've heard of a few issues with the December build but wondering did it fix connectivity for anyone who was experiencing it before that. Thanks
Bxperiaz3 said:
Hi guys, I know this issue has been reported here a bit. It wasn't bothering me too much but recently it seems to have gotten a lot worse. My pixel seems to drop connection pretty regularly and then take a good while to reconnect. I find myself reseting my internet settings a good bit and then it behaves itself for a while before dropping again.
I'm still on October build, but I've gotten a fresh sim card, updated sim manager and I have done the force lte trick but nothings really helped. I spend a lot of my time seeing the exclamation mark on my coverage icons and messing around with settings trying to get it to reconnect.
Am I going to have to return this handset or will an update fix it? Thanks
Click to expand...
Click to collapse
You're literally still on the October fix and asking here if an update will fix it. Just update, and see it for yourself, if it doesn't fix it, it's ultimately your decision if you want to keep the device or not.
ekin_strops said:
You're literally still on the October fix and asking here if an update will fix it. Just update, and see it for yourself, if it doesn't fix it, it's ultimately your decision if you want to keep the device or not.
Click to expand...
Click to collapse
Well I heard people on the December update were having camera issues so I'm asking if anyone with the most updated firmware has connectivity issues as well before I risk it. Seems pretty logical to me.
If you're gonna reply to a question try to be helpful instead of rude, otherwise just don't comment.
Bxperiaz3 said:
Well I heard people on the December update were having camera issues so I'm asking if anyone with the most updated firmware has connectivity issues as well before I risk it. Seems pretty logical to me.
If you're gonna reply to a question try to be helpful instead of rude, otherwise just don't comment.
Click to expand...
Click to collapse
You're asking if an update will fix this issue, and literally, no one can answer this question. So I'm not sure what exactly are you expecting here. I would have already updated to the latest ROM and see if that fixes the issue (factory reset too) instead of relying on speculations from people.
If it doesn't fix it, return or RMA your device instead of "wasting time" waiting for answers like "Yes", "No", "Maybe".
No one is being rude, you're just over-sensitive it seems like, just pointed out an obvious situation here.
ekin_strops said:
You're asking if an update will fix this issue, and literally, no one can answer this question. So I'm not sure what exactly are you expecting here. I would have already updated to the latest ROM and see if that fixes the issue (factory reset too) instead of relying on speculations from people.
If it doesn't fix it, return or RMA your device instead of "wasting time" waiting for answers like "Yes", "No", "Maybe".
No one is being rude, you're just over-sensitive it seems like, just pointed out an obvious situation here.
Click to expand...
Click to collapse
It's not speculation if someone who had known connectivity issues, managed to resolve them with the latest update,which is why I asked. Pretty simple really.
Not being sensitive just don't understand why you're commenting here, wasting my time, if you have no useful advice.
Have a good day
Bxperiaz3 said:
There has been plenty of people with cinnec
It's not speculation if someone who had known connectivity issues, managed to resolve them with the latest update,which is why I asked. Pretty simple really.
Not being sensitive just don't understand why you're commenting here, wasting my time, if you have no useful advice.
Have a good day
Click to expand...
Click to collapse
I literally gave you the MOST USEFUL advice. "Update the phone to the latest, do a factory reset, and see if you have the same issue".
The most logical and reasonable advice one can give you considering the circumstances and what is happening to your device.
Bxperiaz3 said:
It's not speculation if someone who had known connectivity issues, managed to resolve them with the latest update,which is why I asked. Pretty simple really.
Not being sensitive just don't understand why you're commenting here, wasting my time, if you have no useful advice.
Have a good day
Click to expand...
Click to collapse
Dude, just update the phone. That's the best advice we can give your for now,