Something interesting I noticed (For Rogers Users) - Captivate General

I noticed last night after poking around the market, that I had some updates to do. When I went to the downloads page, low and behold there was an update all button at the bottom.
I thought that was a froyo feature only, I have not received the 2.2 upgrade as yet. I suspect that something is coming rather soon.
Keep your eyes peeled.
Q.

This has nothing to do with Rogers. The Android Market was updated. It's been posted here, and just about every other android forum.
http://forum.xda-developers.com/showthread.php?t=863774

It appears as others have caught this as well and managed to beat me to the post!

Related

G1 and mytouch 3g users get android 2.5 update in january

http://droidheaven.com/2009/12/12/g1-and-mytouch-3g-to-get-2-5-update-in-january/
We get the Android 2.5 update in January!!!!! When Cyanogen/Dwang put this into their rom, everything is going to be EPIC
is there any actual proof for this?
if you look at the comments below the article droidheaven even said to go and ask t-mobile. i'm going to do that and hope.
UPDATE: I just talked to a T-Mobile Rep and he said he never heard of a 2.5 update coming in January. He checked and there is no documents. But there is hope. He also told me that there is an update and he won't be surprised if it was 2.5. One more thing. He said it is coming quickly.
LETS KEEP OUR FINGERS CROSSED!!!!
AndroidNoobie said:
if you look at the comments below the article droidheaven even said to go and ask t-mobile. i'm going to do that and hope.
UPDATE: I just talked to a T-Mobile Rep and he said he never heard of a 2.5 update coming in January. He checked and there is no documents. But there is hope. He also told me that there is an update and he won't be surprised if it was 2.5. One more thing. He said it is coming quickly.
LETS KEEP OUR FINGERS CROSSED!!!!
Click to expand...
Click to collapse
boys this is HTC we are talkin about, if ur device is older than 6 or 7months old you get no support whatsoever i was shocked to hear the hero was getting 2.1 so il be amazed if the G1 gets 2.5 i hope u do tho
HTC already gave up on the Dream, however, Android Alliance will never give up on its devices, while T-Mo has to support it at least until it actually has a single device with a different CPU
if only the mytouch gets the 2.5 update can the g1 get it too? i don't mean like OTA update but cyanogen/dwang/someone turns 2.5 into a ROM?
they should really make devices that can go up at least one in updates (like from 1.x to 2.x or somewhere along that line)
AWSOME
This means I loose hope for good touchscreen with Keyboard from Tmobile
YES APPS are back in bussniess
T-mobile G1-Black
All roms from time to time
RA Recovery
coming but not soon iPhone apps on g1 installer.

Got an email this morning from Tec support about 2.2 being available.

I sent them an email a couple of days ago explaining crap thats going on with the phone and how Froyo 2.2 would from what i understand fix most of the problems etc etc. I just wanted to try again to find out about a date. Well i got an email back from tec. upport saying they are glad to announce that the 2.2 update IS available and to call their 800 number for help if i had problems installing. but clicking on the link just brings me to the old FAQ page that they took down. Come on Samsung get a freaking clue. I don't understand why they would send this out and not be true?????
(so maybe things will be rolling out today then because after rereading email i noticed their central time which is 3 hours behind me. So right now my time there still closed) Fingers crossed
Ok so just got of the phone with Samsung. Acording to them and the information they have in their office Froyo 2.2 IS OUT but because theres a problem with the site we don't can't download it yet lol Samsung needs to really get an Fing clue.
I'm pretty sure you need to install that with Kies Mini if it is, indeed, available.
JRd1st said:
I'm pretty sure you need to install that with Kies Mini if it is, indeed, available.
Click to expand...
Click to collapse
Nothing showing up on Kies Mini eather. So again am hoping that things will start rolling out as soon as they open at 9 central time.
I saw another post at AT&T official forum about multiple Samsung reps claim the 2.2 for Froyo is avialable and directed to the same link. Looks like Samsung already trained or released information about Captivate 2.2 release internally, a bit prematurally. So, it seems our UCKB1 ROM will be the official ROM after all. It is just waiting for AT&T to give the final nod.
<--- not holding his breath... Plus, the more I think about it, at this point... What's the point? I mean, 2.2 is rapidly aging and I'm not aware of any newly released devices coming out with 2.1 anymore - They've all got 2.2, which means that 2.3 is the next step.... and with the excellent development we already have, running stable 2.2 is already a reality! I want the update just so the companies are held to their promises, but as for an official 2.2; I'm not going back to ATT bloatware and half ass GPS.
Tried OTA update and it just hung......
I tired to go into media hub yesterday just to see if i missed it being fixed and it hung on checking for update. Checked phone for OTA and it also hung on checking for update. funny thing is about 4 days ago everything was working just fine. Im about to get on the phone with ATT and ***** about the email and when samsung opens and nothing happenes today will be on the phone *****ing about sending false emails to people.
So basically Samsung has just changed the lies from "It will be out soon" to "It's out now but you can't have it"! Way to go Samsung!
UCKB1 has a working media hub. If I were you I'd just install that. It'll probably end up being the official build anyhow.
Bunch of crap Samsung is. wow.....
Just got done talking to live support. what a joke. i have a dam email saying it's out. if you call and talk to someone they say all the info they have says it's out but live says its not and gives you the say crap as before about no info right now. Someone over there needs to get their head out of their ass and get a CLUE.

Docomo SH-03C (Lynx 3D)

Is there any known way of cracking the NAND protection on this phone yet?
Or if not, does anyone know where I should look for the latest news on rooting this Japanese-only phone?
I've been looking all over the internet for months and turned up nothing. I could really do with some help here please guys!
I am also interested in an answer to this question. I have been in talks with a few of the Japanese users currently trying to figure out the phone, and I would like to post a bit about what we know, what progress has been achieved and why this is important for other people outside of Japan.
First and foremost, Sharp has every intention of getting their 3D phones into the hands of overseas users. Now, I could be patient and wait for this to launch, and then for the teams to get to work and crack the bootloader open properly. But why not get an early jump on the work so that the phone can arrive, on the Western shores, fully ready for custom roms and root permissions? The three major 3D phones Sharp currently is pimping (the IS03, the 003SH and the SH-03C) are essentially the same phone with minor tweaks. Serious progress on one could lead to a bit step forward for all! And as the Lynx is currently stuck at 2.1 (and won't be 2.2 till "summer"), it's in the greatest need for an upgrade (the 003SH is already 2.2, and the IS03 goes to 2.2 this week). I know that I'm being a little selfish in this endeavor, but I also know I'm not the only one with this phone, and not the only one interested. Perhaps I'm just the most vocal.
Now, for a quick rundown:
rageagainstthecage: doesn't work, freezes up, phone must be hard rebooted with battery removal.
psneuter: offers root access, but cannot modify /system due to NAND protection/locked bootloader.
SuperOneClick: see above.
Z4root: see above.
Universal Androot: doesn't work. Attempts to root, gets the "no good fuu~~" response.
Visionary: crashes when attempting soft root.
Unrevoked apk: fails immediately. No harm to the phone, but no success either.
gfree: No luck, can't toggle S-off but that may be due to the fact that the phone is definitely not the G2.
Unrevoked app: can't recognize the phone.
I'm hoping that someone in the UnrEVOked community is willing to try and work with me/us on this. We're not a large group by any means (and a majority of the users don't have an expansive English grasp) but we are dedicated, and I'm trying something new everyday. Sharp has even released the kernel as open source, so, if an exploit can be found, work can begin immediately. This could be something big, something wonderful. If anyone could please contact me and let me know, I'm really hopeful.
And sorry for hijacking your thread Eliott.
Sent from my SH-03C using Tapatalk
Sharpen3d said:
I am also interested in an answer to this question. I have been in talks with a few of the Japanese users currently trying to figure out the phone, and I would like to post a bit about what we know, what progress has been achieved and why this is important for other people outside of Japan.
First and foremost, Sharp has every intention of getting their 3D phones into the hands of overseas users. Now, I could be patient and wait for this to launch, and then for the teams to get to work and crack the bootloader open properly. But why not get an early jump on the work so that the phone can arrive, on the Western shores, fully ready for custom roms and root permissions? The three major 3D phones Sharp currently is pimping (the IS03, the 003SH and the SH-03C) are essentially the same phone with minor tweaks. Serious progress on one could lead to a bit step forward for all! And as the Lynx is currently stuck at 2.1 (and won't be 2.2 till "summer"), it's in the greatest need for an upgrade (the 003SH is already 2.2, and the IS03 goes to 2.2 this week). I know that I'm being a little selfish in this endeavor, but I also know I'm not the only one with this phone, and not the only one interested. Perhaps I'm just the most vocal.
Now, for a quick rundown:
rageagainstthecage: doesn't work, freezes up, phone must be hard rebooted with battery removal.
psneuter: offers root access, but cannot modify /system due to NAND protection/locked bootloader.
SuperOneClick: see above.
Z4root: see above.
Universal Androot: doesn't work. Attempts to root, gets the "no good fuu~~" response.
Visionary: crashes when attempting soft root.
Unrevoked apk: fails immediately. No harm to the phone, but no success either.
gfree: No luck, can't toggle S-off but that may be due to the fact that the phone is definitely not the G2.
Unrevoked app: can't recognize the phone.
I'm hoping that someone in the UnrEVOked community is willing to try and work with me/us on this. We're not a large group by any means (and a majority of the users don't have an expansive English grasp) but we are dedicated, and I'm trying something new everyday. Sharp has even released the kernel as open source, so, if an exploit can be found, work can begin immediately. This could be something big, something wonderful. If anyone could please contact me and let me know, I'm really hopeful.
And sorry for hijacking your thread Eliott.
Click to expand...
Click to collapse
Not at all, thanks for the great info!
As crazy as it might sound, one thing I recommend doing is to continue monitoring other roofing methods that aren't exactly for the sh-03c and seeing what happens. Recently a new method for the Thunderbolt has been unveiled, and I have every intention to try it out. Obviously the likelihood of it working is slim, but it's a ton better than running z4root over and over and hoping for different results.
Sharpen3d said:
As crazy as it might sound, one thing I recommend doing is to continue monitoring other roofing methods that aren't exactly for the sh-03c and seeing what happens. Recently a new method for the Thunderbolt has been unveiled, and I have every intention to try it out. Obviously the likelihood of it working is slim, but it's a ton better than running z4root over and over and hoping for different results.
Click to expand...
Click to collapse
I'm a bit hesitant to use untested methods. This is my first Android phone and I have never rooted a phone before so it would be wise for me to wait for someone else to find a reliable way first.
I have flashed many older phones and PSPs in the past but this scene is quite new to me.
I am still checking many Japanese sites daily for news of a root. I will send you a PM if I find anything
figured to bump the thread as I`m also a Lynx3D owner looking for root access and a way around the NAND protection. I would be nice to free up this phone .
I'm still searching daily but it seems to be impossible, I'm not sure if it will ever be rooted.
Never mind though, at least we get android 2.2 this month
Recently there's been some success for the IS03 since receiving their 2.2 update. A new process labelled is03break has apparently been great for soft rooting. It hasn't worked on the SH-03 due to it still being on 2.1, but perhaps there will be a breakthrough after our update drops in June (July?).
Additionally, certain other blogs (specifically the Japanese blog Androot) has reported a failure in attempting all conventional root methods, confirming that the Japanese teams are on the same page we are. Both good and bad, as it does give us a baseline, but I refuse to accept there isn't a solution yet.
Sharpen3d said:
Recently there's been some success for the IS03 since receiving their 2.2 update. A new process labelled is03break has apparently been great for soft rooting. It hasn't worked on the SH-03 due to it still being on 2.1, but perhaps there will be a breakthrough after our update drops in June (July?).
Additionally, certain other blogs (specifically the Japanese blog Androot) has reported a failure in attempting all conventional root methods, confirming that the Japanese teams are on the same page we are. Both good and bad, as it does give us a baseline, but I refuse to accept there isn't a solution yet.
Click to expand...
Click to collapse
That certainly gives me hope, looking forward to 2.2 even more now!
And Docomo have announced that 2.2 is coming this month (May). It has been widely reported and they confirmed it in the Docomo shop this morning for me
Despite my better judgement, I went ahead and ran the is03break on my phone yesterday. Not only was it not successful (ran until it timed out) but it managed to adjust my settings enough that my phone wasn't able to see the cellular network, effectively destroying it's "phone" capabilities. I was able to hard reset it through psneuter/adb and now it's back to normal, but it was definitely a bit of a scare.
When 2.2 comes out, I may give it another go, but in the meantime I'll just play nice. Docomo staff confirmed 2.2 is coming before the end of May, and there's a chance we'll need to do it through the PC like the AU folk had to.
Looks like the update may well have been delayed until next month -
http://translate.googleusercontent.com/translate_c?hl=en&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26client%3Dfirefox-a%26hs%3DG75%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26tbs%3Dqdr:d%26prmd%3Divns&rurl=translate.google.com&sl=ja&twu=1&u=http://juggly.cn/androidrumors&usg=ALkJrhgmfYRu8El9AjAHz_UeNb1s85EhZw
This is getting a bit much now. 6 months I've been waiting for them to update this phone. I'm considering taking it back and demanding a refund.
For what it's worth, even if there's a delay, at least it's a bit more definitive than things have been. Way back in March when the Quake hit, we were told it was being delayed from March to "Summer." Then they really brought it forward for May, which I don't really consider summer. That rumor blog (and remember, the key word there is rumor) suggests it will be delayed until early June. Worst case scenario, that means that, instead of getting it this week, we receive it in two weeks. I agree it's a pain in the ass, and the fact remains that, stuck at 2.1, we can't use a lot of conventional rooting tools (not to mention run flash, do App2SD, JIT, etc). But returning the phone at this point accomplishes next to nothing. The summer Docomo lineup is a bit underwhelming, in my opinion. You're paying for the camera, and the phone is attached to that. Even if you get the Galaxy S (a really nice phone, no doubt) it's starting to become a bit older. IF we can hold on till SH-03C receives 2.2, I honestly believe a world of possibilities open up. This community may not be large, but we can still tout a 3D phone proudly, and getting 2.2 really legitimizes its abilities.
Just be patient man.
Yeah, you are right.
I'm just getting frustrated at having to keep deleting applications. I'm really looking forward to using flash, bumping up the CPU and trying out that new Tegra app for playing Tegra games!
I'm just really hoping for App2SD. This is getting severely limiting. Additionally, I'm pretty sure that rooting will become significantly more likely once we're up on 2.2. I'm confident that, once we get to Froyo, our phones might be able to piggyback on methods utilitized by other NAND locked phones (example: EVO) that have been successfully rooted.
I just want to uninstall that stupid 3D golf game. It takes up so much memory it's insane.
This sounds promising -
"May 27, 2011
The previous model, LYNX 3D SH-03C in Android 2.2 update seems to be out soon. The details will be announced separately, "there is no update, that will never" Yes."
http://translate.googleusercontent.com/translate_c?hl=en&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26safe%3Doff%26client%3Dfirefox-a%26hs%3D5Ye%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26biw%3D1120%26bih%3D927%26tbs%3Dqdr:d%26prmd%3Divns&rurl=translate.google.com&sl=ja&twu=1&u=http://ch00288.kitaguni.tv/e1805281.html&usg=ALkJrhgPutM5T2orqoipGRQTi3kSISqnlg
The woman at the Docomo helpline, having started to recognize my voice, totally leveled with me. The update was planned for the end of this month, and they got screwed in timing. They hope for the first weeks of June, but it may be even later than that. Truth be told, I bought my SH-03c aftermarket, so I can't return it even if I wanted to. But I'm not bailing. I'm confident we will see the update before the 15th, and, really, as long as it doesn't start malfunctioning, I can wait.
More rumors, looks like July 7th is the day -
"NTT DoCoMo's "Galaxy S SC-02B", "Galaxy Tab Sc-01C", "LYNX 3D SH-03C" on the OS version is effective from June 7, "will" is a rumor.
According to rumors, the version of June 07, Galaxy S Tab and the Android 2.3 (Gingerbread) to, LYNX 3D SH-03C is Android 2.2 (Froyo) is going to be provided.
LYNX 3D SH-03C
Changes as part of the Android 2.2
-Flash Player 10.1 or later for
- Micro SD card can move the app (the app only support)
- Respond to voice the character input
- Application for Automatic Updates to bulk update
- The application "search" and "News and Weather," in some of the sharp changes in their own additional
- Launch applications list "end all" button added
- Power management notification bar menu (Wi-Fi or BT) is added
- Supports multi-line display in the profile email address and telephone chat
- Added ability to integrate similar contacts in the phone book
- Added the ability to transmit infrared applications infrared receiver
- Change the background color
- Change display Antenapikuto
- Text resize cursor display
- Improved slightly phenomenon events
How to update, download the update tool from the site WEB Sharp, PC and USB connection seems the only way to do. "
http://translate.google.com/translate?hl=en&sl=ja&u=http://maruta.be/news_japan_2100/828&ei=Pq7jTdb4DYuSuwP4x_D0Bg&sa=X&oi=translate&ct=result&resnum=8&ved=0CG4Q7gEwBw&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26safe%3Doff%26client%3Dfirefox-a%26hs%3Dvf4%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26biw%3D1120%26bih%3D927%26tbs%3Dqdr:d%26prmd%3Divns
That makes a ton of sense. June 7th is when Nintendo is launching a huge update for their platforms as well, and Japan seems to like to do a ton of updates all together.
I want this so badly, I can't believe it's going to be another week.
The product page for the SH-03C over at nttDOCOMO just went 404. I really hope it's because they're busy updating with new information, and not because I'm going to be furiously angry.

[Q] voice search bug but no OTA update yet

I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?
Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.
The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box
ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S
3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.
I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.
I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny

[Q] Just got Shield (32GB), It has 4.4.2, says OTA "1.21" available...

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....

Categories

Resources