As any of you who have tried to install a MicroSD card know, there was a little place holder that said "Replace with MicroSD only after Android system update".
There is no info on the Motorola page other than repeating that message. I haven't gotten any response to questions about time line for update.
Any one know more?
Ballzdeeeper said:
As any of you who have tried to install a MicroSD card know, there was a little place holder that said "Replace with MicroSD only after Android system update".
There is no info on the Motorola page other than repeating that message. I haven't gotten any response to questions about time line for update.
Any one know more?
Click to expand...
Click to collapse
One day...your guess is as good as everyone elses. When we send them in for the 4g fix, then the sdcard should work when it gets back is the way i understand it. I have put sdcards in there, and it does nothing can't even see it from the pc.
My guess is they would need to get the MicroSD 'issue' fixed before they release the Wifi version. Since that version is not going to be sent back for the 4G LTE hardware change. But if there is ANY part of it attached to the hardware that will be swapped out in the 3G/4G model, then they may have to have separate release dates depending on Wifi-only versus 3G/4G models.
The Wifi versions may get the 'support/fix' before 3G then if that's the case.
So here is hoping there will be some update around early April with the rumors of an April 3rd (or maybe late March) Wifi launch date.
This is a software issue only it has nothing to do with the 4g upgrade which only adds a mini-pci card to the board.
Everyone will get this update, 4g or not.
Sent from my PC36100 using XDA Premium App
Good and bad then I suppose.. if it is just software.. it means the date is still up in the air. Bummer.
if that's the case and the wifi versions would be fixed ahead of time before launch so they don't have to send them back wouldn't you think this is something they can OTA a hotfix for? Like a little patch to enable it and fix whatever issue it's having (if there truly is one).
Well, if it truly was a hardware + software issue (which Bauxite replied it is only sw) then I was imagining Moto 'fixing' the hardware issue and Google/Moto combining that with a software fix. So, no, I don't think an OTA would have fixed it if it was HW+SW. Anyways.. moot now.
any updates on this?
Related
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.
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
Anyone have thoughts on what the new firmware is for the P3113? I just got an alert on my rooted device that I have a new firmware upgrade.
another useless update that I don't need?
I just checked for an update on my tablet and there doesn't seem to be one available. But if there is soon I will let you know of any obvious changes.
dansskittles said:
I just checked for an update on my tablet and there doesn't seem to be one available. But if there is soon I will let you know of any obvious changes.
Click to expand...
Click to collapse
Thanks! I appreciate it.
You can download it here http://samsung-updates.com/device/?id=GT-P3113
Just not sure if it's worth it, and what will happen since I am rooted. It's not a full upgrade to JB which I know I would need to do an FDR for, but just a minor update (which could be leading to JB later on down the road, there have been 2 updated in the last 30ish days, thats usually a good sign, from past device experiences at least lol).
Perhaps HDMI support and/or UMS support for the external sd card? I can dream, can't I...
Dreams do come true, they can happen to you...
rsage said:
Perhaps HDMI support and/or UMS support for the external sd card? I can dream, can't I...
Click to expand...
Click to collapse
I love your dreams, and I share those dreams with you too. Let me know if I should buy a lotto ticket, since it would be a nice lucky day.
If it where HDMI support I would suspect we would see an adapter available on Samsung's website for this tablet. Since there is none I'm guessing its something more mundane. However my tab is charging up now in preparation of the update and will let you know as soon as I can.
So I installed the update and right off the bat nothing jumped out at all lol. So I went through to find changes and kinda came up with nothing. I could probably do some more serious digging to find what has been changed. If you have anything you want me to test with it I will just let me know.
App to SD?
dansskittles said:
If it where HDMI support I would suspect we would see an adapter available on Samsung's website for this tablet. Since there is none I'm guessing its something more mundane. However my tab is charging up now in preparation of the update and will let you know as soon as I can.
So I installed the update and right off the bat nothing jumped out at all lol. So I went through to find changes and kinda came up with nothing. I could probably do some more serious digging to find what has been changed. If you have anything you want me to test with it I will just let me know.
Click to expand...
Click to collapse
That would be the only thing I could want to see to be honest since nothing else has lol. I think it might be a primer update to go to JB in the next month or 2, which means I'll have to go back and update through since I am rooted and shouldn't try to update till unrooted.
Then again I could be 100% wrong, so don't pin hopes on my theory lol.
Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....
I couldn't find anything anywhere online about this OTA that I got yesterday on my US996, no record of it ever existing. So I asked LG about it and this was their response. I haven't applied the update yet, but will update this post if I notice anything other than what LG stated. I will hold off for a while on installing it so if enough people want me to capture and share the OTA then I will.
https://www.youtube.com/watch?v=KsD3pGv5cv8
From what I see all I've noticed is the Nov 6 security patch which means blueborne and krack are fixed among other exploits, ARB is still 0 so can be rolled back if wanted for some reason. Cool that it adds rcs support, not that my carrier has support anyway
was there a point for a video? simple screenshot of the conversation would have sufficed
updated, and i can't use my sim card anymore, the phone detected sim card but no signal at all, got some extra buttons in dailer.
ttnduy said:
updated, and i can't use my sim card anymore, the phone detected sim card but no signal at all, got some extra buttons in dailer.
Click to expand...
Click to collapse
As I mentioned in another thread, after I installed the update, it listed "unknown version" for baseband and wouldn't connect to Verizon for a few minutes. Then the baseband version showed correctly and it connected.
Since baseband is a wholly separate CPU and OS, it's not clear what it was updating in the background, but it fixed itself eventually.
alexandero11 said:
I couldn't find anything anywhere online about this OTA that I got yesterday on my US996, no record of it ever existing. So I asked LG about it and this was their response. I haven't applied the update yet, but will update this post if I notice anything other than what LG stated. I will hold off for a while on installing it so if enough people want me to capture and share the OTA then I will.
https://www.youtube.com/watch?v=KsD3pGv5cv8
Click to expand...
Click to collapse
Obviously LG thinks that we don't need to know the details, just that LG has improved the usability and functionality of the phone, that's all we need to know. /s
From what I can tell, it's the same build of android, NRD90M, as before the update. So probably only has google supplied security patches.
As long as LG gives us US996 Unlocked users an Oreo update early next year, I'm OK with them not doing much with the original 7.0 firmware... but definitely security updates more than once per year would have been nice.
The "slower than" or "completely missing" compared to major carriers updates up until this one, has definitely been a disappointment since the factory unlocked version of the phone should be the easiest to get updates pushed out for.