Database Info

New AT&T Firmware Push?

Got a text this morning stating an update was coming from ATT.
Is this Froyo or just a GPS fix?

http://forum.xda-developers.com/showthread.php?t=882714

Nope 99.999999% sure its still JH7 OTA

wmwilker said:
Got a text this morning stating an update was coming from ATT.
Is this Froyo or just a GPS fix?
Click to expand...
Click to collapse
That will be too nice of AT&T. No, you only get such notification TWO months AFTER the update has been pushed out. In this case, it is the old JH7 update.

Doesn't matter anyway, I'm running Doc's V6.1 2.2.1 JPY

I've been seeing this same topic repeatedly being brought up more so since the Nexus S came out. I figured I'd make an attempt and try to talk to someone semi official about it. See below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, at least that chat seems to put paid to the idea we'll be getting 2.2 in 2010.

I also recieved 3 texts this morning about this, but my phone cannot connect to ATT servers so I called them to ask what this was all about. I'm on the newest JH7 as I just got this as a replacement phone a few weeks ago. I kept this new phone unrooted and unmodified for the moment to see if any new OTA's would load to my phone as I had issues with the OTA for JH7, I believe that I used DG's update.zip on the old phone to get it. Anyway, I told the tech at ATT what version that I was running and if they were really trying to push a new update out. He stated that it is a new update and the reason that I can't connect to the servers is that they are probably overloaded now with others trying to download it. I also asked if it is the 2.2.1 update and he said that he believes so, but no definitive answer as of yet. And yes, I'm also sick of a new thread about a possible update every day, so that's why I called ATT and figured that I'd share what I found out with our community. I just hope that the tech is correct in assuming that it is 2.2.

dwanhala said:
I also recieved 3 texts this morning about this, but my phone cannot connect to ATT servers so I called them to ask what this was all about. I'm on the newest JH7 as I just got this as a replacement phone a few weeks ago. I kept this new phone unrooted and unmodified for the moment to see if any new OTA's would load to my phone as I had issues with the OTA for JH7, I believe that I used DG's update.zip on the old phone to get it. Anyway, I told the tech at ATT what version that I was running and if they were really trying to push a new update out. He stated that it is a new update and the reason that I can't connect to the servers is that they are probably overloaded now with others trying to download it. I also asked if it is the 2.2.1 update and he said that he believes so, but no definitive answer as of yet. And yes, I'm also sick of a new thread about a possible update every day, so that's why I called ATT and figured that I'd share what I found out with our community. I just hope that the tech is correct in assuming that it is 2.2.
Click to expand...
Click to collapse
No, he's not. I just checked with Kies and the update is still the one rolled out back in September. Nothing to see here. Carry on.

dwanhala said:
I also recieved 3 texts this morning about this, but my phone cannot connect to ATT servers so I called them to ask what this was all about. I'm on the newest JH7 as I just got this as a replacement phone a few weeks ago. I kept this new phone unrooted and unmodified for the moment to see if any new OTA's would load to my phone as I had issues with the OTA for JH7, I believe that I used DG's update.zip on the old phone to get it. Anyway, I told the tech at ATT what version that I was running and if they were really trying to push a new update out. He stated that it is a new update and the reason that I can't connect to the servers is that they are probably overloaded now with others trying to download it. I also asked if it is the 2.2.1 update and he said that he believes so, but no definitive answer as of yet. And yes, I'm also sick of a new thread about a possible update every day, so that's why I called ATT and figured that I'd share what I found out with our community. I just hope that the tech is correct in assuming that it is 2.2.
Click to expand...
Click to collapse
OMG, you believe a tech that says " he believes so".
When the push comes down, i'm still betting on St. Patrick's Day, you'll know about it. It'll be all over the internet.

Yep, I'm an idiot.............trusted ATT, didn't want to fall in to that trap. Worst part is, that I should've know better, I've even followed the numerous other posts. Anyway, this afternoon I chatted to another rep and I guess that they were trying to push the JH7 update to my phone even though it came to me preloaded, which makes complete sense

The second rep stated it wouldn't be available until next year....
Sent from my SAMSUNG-SGH-I897 using XDA App

Don't feel bad guy's, Roger's official stance is sometime in the first half of next year. You got it lucky.

TheEscapist said:
Don't feel bad guy's, Roger's official stance is sometime in the first half of next year. You got it lucky.
Click to expand...
Click to collapse
Perhaps Rogers is just being more honest/realistic......I wouldn't be shocked if we don't see it for quite a while either.

Never have got a text message about updates but I did get a email from Samsung to advise me the Media Hub is coming soon!

newter55 said:
Perhaps Rogers is just being more honest/realistic......I wouldn't be shocked if we don't see it for quite a while either.
Click to expand...
Click to collapse
You clearly didn't see the debacle that was the Canadian Captivate launch. Bell and Roger's both announced their SGS phones around the beginning of August, Bell had theirs out in a week, Roger's said within the month. No one got their phone until November. I don't remotely trust anything they say, and besides, they said this before their phone even came out.

amazed that people (that frequent XDA forums now less) would be so heartbroken about lack of official froyo.
sure i will probably take the official release for a spin when it gets here but i am guessing it won't last more than 24-48 hours before i re-flash a custom 2.2 or custom gingerbread which may here before official 2.2.
There have been multiple quality roms froyo roms available for months...and most of them i am betting offer more in the way of speed and in many cases stability than the official bloated version will.
Why not stop opining and learn how to put your phone to its full potential?
(I know some will say they don't want to void there warranty and shouldn't have to.....that latter of which i agree with.....but if your afraid of rooting and flashing why would you be @ XDA?)

bames said:
...but if your afraid of rooting and flashing why would you be @ XDA?)
Click to expand...
Click to collapse
I get kinda tired of seeing this same response in here. There's a lot more to this place than just ROM flashing and rooting. I have found a ton of info, mods, apps and upgrades in here for my Incite, Tilt 2 and now my Captivate and have never flashed a ROM on either of them. There is so much more to XDA than just cooked ROMs and insisting otherwise is just ignorant.

When you rule out modes that require a rooted device....probably 90% of whats posted in the forum involves a process that "voids" your warranty.
If someone wants froyo so badly they should install it. It is available to them and is faster and as or more stable than the stock 2.1 releases (+ most of them have improved gps performance).
The same people who post day in day out their need and want for froyo will move on to do the same thing about gingerbread within 24 hours of having their official froyo while most of the visitors here will already be running gingerbread courtesy of the rich development community @ XDA.
Do i think its stupid that it takes them so long to push and official release....yep...but it seems to be an issue that has been a problem more for android as a whole than for just samsung or att. The same thing that make android great the open nature and a variety of handsets is the same thing that hinders prompt updating of new firmware. I see it being the biggest thing that could hurt android in the long run. I think it also one of the reasons we have a much weaker selection of high-end games for android devices. The gaming potential of the galaxy s line-up is much greater than the iphone but developers seem hesitant go all in to develop for the platform.

bames said:
Do i think its stupid that it takes them so long to push and official release....yep...but it seems to be an issue that has been a problem more for android as a whole than for just samsung or att. The same thing that make android great the open nature and a variety of handsets is the same thing that hinders prompt updating of new firmware. I see it being the biggest thing that could hurt android in the long run. I think it also one of the reasons we have a much weaker selection of high-end games for android devices. The gaming potential of the galaxy s line-up is much greater than the iphone but developers seem hesitant go all in to develop for the platform.
Click to expand...
Click to collapse
The late releases are going to plague any developer they always have and always will. All we can do is hope its a quality one so we don't have to downgrade till they fix the new bugs. Galaxy s is a fairly new line compared to the iPhone and while superior its going to take a while for big game developers to get there feet wet. They haven't had as much time support or desire to try something new when they have there old faithfuls. I do think android is a lot better that iPhone speaking from experience on all platforms but there is pros and cons coming from development and Apps on both sides.

Vibrant getting Froyo tomorrow -- Offical.

http://gizmodo.com/5739026/samsung-galaxy-s-vibrant-getting-android-22-froyo-tomorrow-says-t+mo
Awesome!
"Going forward, Brodman explained, Samsung hopes to keep all handsets up to date within 3 to 5 months of Google releasing a new version of the OS. "
Lets hope they stick to that.

so, samsung has had the 2.2 upgrade out since november...
well if it took tmo all this time to add wifi calling, since att doesnt have that feature one can REASONABLY assume that ATT is just run by douches.

It's safe to assume that anyway.
But good for our Vibrant brothers and sisters. Maybe this is the beginning of the end of Samsung and the carriers dragging ass on these upgrades, but who knows. They better get to work on Gingerbread if they want to keep that 3-5 month schedule.
Sent from my SAMSUNG-SGH-I897 using XDA App

Here's the original post: http://www.pcmag.com/article2/0,2817,2376045,00.asp
"So what was the hold-up? It was purely technical, Brodman said—it wasn't about marketing, payments or sales. Samsung sent its base 2.2 upgrade to T-Mobile in late November, and with the holiday season, it's taken until now for T-Mobile to work out the kinks and integrate its own features."
When will these carriers realize that loading phones with their bloatware does no good! Simply release the plain base 2.2 update!

ipxnsv said:
http://gizmodo.com/5739026/samsung-galaxy-s-vibrant-getting-android-22-froyo-tomorrow-says-t+mo
Awesome!
"Going forward, Brodman explained, Samsung hopes to keep all handsets up to date within 3 to 5 months of Google releasing a new version of the OS. "
Lets hope they stick to that.
Click to expand...
Click to collapse
3-5 months. Yeah, that's totally happening.
Sent from my Samsung Galaxy S using XDA App

its pretty clear in the case of the vibrant that t-mobile deserves the brunt of the blame for the hold up as they have had their hands on the update since september.
Is there any reason to believe att hasn't had the update in their possession just as long?
not to absolve samsung but they have taken most of the abuse on this and it looks like the carriers are the hold up at this point and have been for 2.5-3 months

bames said:
its pretty clear in the case of the vibrant that t-mobile deserves the brunt of the blame for the hold up as they have had their hands on the update since september.
Click to expand...
Click to collapse
The article says late Nov., not sept.
Is there any reason to believe att hasn't had the update in their possession just as long?
Click to expand...
Click to collapse
According to one of the screenshot posted on AT&T web site, our Froyo version is UCJK1. We got first Froyo leak late sept, UCJI6. Second in late Oct., UCJJ4. So, UCJK1 should be around late Nov.
So I guess AT&T had the Froyo build the same time as T-mo.

According to one of the screenshot posted on AT&T web site, our Froyo version is UCJK1. We got first Froyo leak late sept, UCJI6. Second in late Oct., UCJJ4. So, UCJK1 should be around late Nov.
So I guess AT&T had the Froyo build the same time as T-mo.[/QUOTE]
Can you post a link pls

Pmac25 said:
Can you post a link pls
Click to expand...
Click to collapse
Last picture in this link http://www.wireless.att.com/answer-...e=en_US&_dyncharset=UTF-8&solutionId=KB110797

Ah, false advertising I see.

jaimingandhi said:
Here's the original post: http://www.pcmag.com/article2/0,2817,2376045,00.asp
"So what was the hold-up? It was purely technical, Brodman said—it wasn't about marketing, payments or sales. Samsung sent its base 2.2 upgrade to T-Mobile in late November, and with the holiday season, it's taken until now for T-Mobile to work out the kinks and integrate its own features."
When will these carriers realize that loading phones with their bloatware does no good! Simply release the plain base 2.2 update!
Click to expand...
Click to collapse
Agreed! They should include a digitally signed file or something per carrier that labels the phone for what carrier and model and then they can upload their scrap to the marketplace. That way the app wont work unless you are on stock carrier os with signed file and the app could verify the correct file info.
Sure it could be ripped from the os but if att had their way id still be on stock 2.1. But for the small amount of users who is mainly comprised of us here at xda, carriers wont have to worry as most people probably do not root their phones.
Sent from my SAMSUNG-SGH-I897 using XDA App

Woah, looks like somebody leaked the screenshot of Froyo on the Captivate. Maybe AT&T has a surprise for us very soon? Who knows.

Looks like Sprint will be following T-Mobile's lead.
http://phandroid.com/2011/01/20/sprint-reassures-samsung-epic-4g-froyo-update-is-coming-asap/

i doubt the captivate is going to get 2.2, ATT is miserable slow with their upgrades and theres not enough push on twitter..the tmobile users bombarded the samsung and tmobile twitter accounts with requests...i dont see the same amount of effort on the ATT side

j3500 said:
i doubt the captivate is going to get 2.2, ATT is miserable slow with their upgrades and theres not enough push on twitter..the tmobile users bombarded the samsung and tmobile twitter accounts with requests...i dont see the same amount of effort on the ATT side
Click to expand...
Click to collapse
because anyone that cared enough just rooted their phone

Seems like a few people that trusted Samsung all along *cough* weren't so dumb after all.

i897ucjk1?
I'll turn to i9088znkp2. Let att eat sh*t

follow the bouncing ball, so to speak.
Removed from Vibrant Forum.

Let's take a look at my last phone... the Samsung Epix (quit laughing at me).
Installed with WinMo 6.1 out of the box with the promise of 6.5 in the coming months.
Phone works pretty well, great GPS, however some people are having a random error appear on their phone, the dreaded "Slog dump".
ATT/Samsung announce update, everyone gets excited about 6.5... except it isn't. It's to fix slog dump error, which it does - while totally crippling the GPS. Instead of an instant lock on 8+ satellites, several minutes of waiting might get you 4 or 5.
The promised deadline of the 6.5 update comes and goes. again and again and again and well you get the idea.
Finally after everyone has given up (or turned to XDA) the official update is released. The GPS is restored and works better than ever before, and Microsoft has already announced wp7, making our update already obsolete.
At this point I have swore of Samsung forever, at least until the Captivate shows up for free at Radio Shack.
lesson learned?
Good things come to those who wait
or probably better
those who don't learn from the past....

I contacted Samsung today regarding a Froyo update for the Captivate. Take a look at the image below.
Hey, I tried right?????????
*Edit* - Sorry about the size. Thought it would auto re-size
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Done with LG

LG can kiss my ass. After over 2 hours of trying to upgrade the damn baseband the tool still keeps messing up. This is insane. They should have gotten it right the first time. I'm done with LG. Notice the time lapse of my second attempt to upgrade this ****. ICS is more stable on my htc hd2. I'm pretty sure I'm now soft bricked. Good luck to the rest of you dealing with this nightmare of a phone. I'll be using my hd2 till I order a galaxy nexus. Also if you know what the problem could be please let me know. I have all of the drivers and its a brand new windows 7 pc I'm using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you reboot both items and make sure you follow directions to the "T" in the threads for this stuff. Also look into other ways. And finally this didn't need its own thread lol, but I understand the need to vent, again read through the threads and you'll see people having your issue and then you'll probably find your solution. Also make sure you are bone stock recovery and all I can't remember if that was a problem or not for some.
Sent from my LG-P999 using xda premium

You could try the kdz app. Also upgrading the bb breajs bluetooth in every rom except stock. I actually upgraded mine and ended up down grading with kdz. New bb is only good if you stay stock or dont need bluetooth calling at all.

I know i was just curious to see how much it would improve the device. I know its only for gps but i was just curious. Anyway, ill look into flashing cwm tomorrow and just keeping the july baseband. I was just pissed because there is only so many errors a person can take before they vent. Thanks guys. I noticed that the ics roms are solvong data drops. Hopefully it becomes more useful to me.

zachpozniak said:
I know i was just curious to see how much it would improve the device. I know its only for gps but i was just curious. Anyway, ill look into flashing cwm tomorrow and just keeping the july baseband. I was just pissed because there is only so many errors a person can take before they vent. Thanks guys. I noticed that the ics roms are solvong data drops. Hopefully it becomes more useful to me.
Click to expand...
Click to collapse
Dont let it fool you, the new bb doesnt help gps, it still sucks. The only improvement it gave is that i was told i sounded louder to someone on the other end than i did on the old bb.

The newer bb also breaks bluetooth unless they fixed that. I'd stay away from the newer bb (maybe that's only on the ICS roms).
But I 100% agree with you, this phone should've been recalled. It would've been 1000x better for LG to cut their losses and recall the phone than to ruin their entire image for themselves. See you on the other side of this P.O.S. Goodluck!

Also disable any firewalls/antivirus. I was having similar trouble until I disabled everything.

Thanks. Yeah it sucks because this phone has a lot of potential but ****ty support. Maybe ill try disabling it and going for one more try. But i think im just gonna stick with the old baseband.

New bb is good in my opinion, but not really worth changing. To much risk for a phone that will eventually have little support, but the devs we do have are awesome and they support the new bb. Love my g2x,but can't wait to upgrade.
Sent from my LG-P999

I got my G2x the day it was released. I was so excited... All went down hill from there. I appreciate all the devs that worked on our phones, but today I ordered a nexus. I just can't take it anymore.
Sent from my LG-P999 using xda app-developers app

Are you on a stock rom?

Blazing angel said:
Are you on a stock rom?
Click to expand...
Click to collapse
If you are asking me, no. I have tried them all. I'm currently on CM7, it's the best on my phone. It still had lots of issues though.
Sent from my LG-P999 using xda app-developers app

I think it's about time for me to move on from the G2X. Too many problems still after all this time. Maybe the SGS3 will suit me better.
Sent from the nether regions of the black abyss under the battery of a G2X.

jnralp00 said:
If you are asking me, no. I have tried them all. I'm currently on CM7, it's the best on my phone. It still had lots of issues though.
Click to expand...
Click to collapse
CM7.2 was a nice little update.. until I overslept for work because my phone had another SOD. I noticed if I leave my Wifi or bluetooth on- it will sometimes SOD... i just have to make sure i turn those two radios off... its only happen 3 time since I updated about a month ago(?). maybe i'll go back to 7.1... i just hate reinstalling the apps even with Titanium backup..

AchilliesOmega3 said:
CM7.2 was a nice little update.. until I overslept for work because my phone had another SOD. I noticed if I leave my Wifi or bluetooth on- it will sometimes SOD... i just have to make sure i turn those two radios off... its only happen 3 time since I updated about a month ago(?). maybe i'll go back to 7.1... i just hate reinstalling the apps even with Titanium backup..
Click to expand...
Click to collapse
Must be some app you are running
Sent from my LG-P999 using xda premium

Nvdia too
The biggest barrier, IMO, is Nvidia's refusal to release driver code or binaries to support the chipset that runs our phone's graphics. I for one am not buying Nvidia's stuff again.

gpmartinson said:
The biggest barrier, IMO, is Nvidia's refusal to release driver code or binaries to support the chipset that runs our phone's graphics. I for one am not buying Nvidia's stuff again.
Click to expand...
Click to collapse
i said that too until i bought my Xoom a few days ago LOL
to the OP - do you have the stock recovery and stock firmware on your phone? if so have you tried the OTA update? this is how i did it
http://forum.xda-developers.com/showthread.php?t=1696266

[Q] Is Nexus 5's design faulty?

After three-four days of usage I noticed considerable flicker on the screen.
I have tried factory resetting, turning off auto-brightness, turning off wifi. But nothing worked.
After some googling I have come to know that this is very frequent issue on nexus 5. There is huge number of threads online discussing the same. Below are some:
https://code.google.com/p/android/issues/detail?id=36417
https://productforums.google.com/forum/#!topic/nexus/o_Hj782Y_aY
http://www.reddit.com/r/Nexus5/comments/2448ws/weird_screen_flickering/
http://forum.xda-developers.com/google-nexus-5/help/screen-flicker-t2525881
http://androidforums.com/nexus-5/841381-nexus-5-screen-problem.html
http://community.koodomobile.com/koodo/topics/my_new_nexus_5_screen_keeps_flickering
http://bragnews.com/nexus-5-flickering-screen-fix/
In fact a user comment "#26 ndend.. @gmail.com" on below thread says that he got nexus 5 replaced 5 to 6th time for similar sounding issue:
https://code.google.com/p/android/issues/detail?id=36417
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I prepared a youtube video of my Nexus 5. Here is what is happening with me:
After more googling I came to know that google and LG has made some redesign of Nexus 5 to fix hardware issues, though silently:
http://www.fonearena.com/blog/90868...-issues-with-nexus-5-with-minor-redesign.html
So I believe both Google and LG knows that Nexus 5 has got some faulty design, but not just putting it straight to media but silently pushing the update in new devices.
In fact Google is replacing older Nexus 5 if you screw its screen, surprisingly by suddenly changing its accidental damage protection policy:
http://techcrunch.com/2014/09/03/ye...-replace-your-nexus-5-if-you-bust-the-screen/
Also some sites went on listing some mostly reported issues with Nexus 5:
http://au.ibtimes.com/articles/524834/20131125/lg-nexus-5-top-10-encountered-issues.htm#.VAm5MPldWb8
http://www.digitaltrends.com/mobile/nexus-5-problems/#!bP8d5j
Now I can feel that this is because Google want to take back some old design bad Nexus 5 back.
Am not at all a designer or electronics professional but from what I can read from this is that there is something wrong with the design of Nexus 5, something is definitely failing its screen stability, either a hardware issue or driver incompatibility.
I wish I could have realized this earlier before buying one.
Now I am in confusion whether to ask for replacement or refund, since I cant find any other flagship running stock android. The only one - Nexus 5 running stock android has these many issues. Is there any other? My requirements are 5"screen, 2 GB RAM, Quad Core Processor.

just get a replacement, got 3 N5 since release without that problem.
or get a refund and wait for newer nexus, if there are one
p.s. G3 is also a good choice if you don't mind.

DummyPLUG said:
just get a replacement, got 3 N5 since release without that problem.
or get a refund and wait for newer nexus, if there are one
Click to expand...
Click to collapse
without "that" problem..means you had different ones? And 3 different or in replacement you got 3rd one?

if you want, by also googling, you can find that aliens have taken over the earth.
i dont have sich issues with my n5, and the majority dont as well. some of the issues are even non issues. only a very small % actually see real issues. you can find info like this for any product. no device is perfect.

DummyPLUG said:
p.s. G3 is also a good choice if you don't mind.
Click to expand...
Click to collapse
Does G3 runs stock android?? Will it get quick updates in future and dont want get into rooting and custom ROMs.
Also Moto G do also get updates right? It also runs stock android?

Mahesha999 said:
without "that" problem..means you had different ones? And 3 different or in replacement you got 3rd one?
Click to expand...
Click to collapse
I mean I have 3 Nexus 5, all of them don't have any screen issue.
---------- Post added at 05:12 AM ---------- Previous post was at 05:08 AM ----------
Mahesha999 said:
without "that" problem..means you had different ones? And 3 different or in replacement you got 3rd one?
Click to expand...
Click to collapse
Mahesha999 said:
Does G3 runs stock android?? Will it get quick updates in future and dont want get into rooting and custom ROMs.
Also Moto G do also get updates right? It also runs stock android?
Click to expand...
Click to collapse
what you mean "stock android" ? if you refer to something like google play edition or AOSP, then no. I don't know the future, but every device will stop updating someday, include nexus.
and sorry, dunno anything about the Moto G.

Mahesha999 said:
In fact a user comment "#26 ndend.. @gmail.com" on below thread says that he got nexus 5 replaced 5 to 6th time for similar sounding issue:
https://code.google.com/p/android/issues/detail?id=36417
Click to expand...
Click to collapse
That's a complaint about the Nexus 7.

Wakamatsu said:
That's a complaint about the Nexus 7.
Click to expand...
Click to collapse
jeez, its even the old nexus 7. look at the date, 11/17/2012.

Huh, it's been 10 months or so and I've never seen a flicker on mine.

Some are just plain faulty, get it replaced and hope that the replacement works well!
Sent from my Nexus 5 using Tapatalk

Every mass produced product is going to have some defective units. Even with good QC, they cannot test every single unit thoroughly, it is impractical and would end mass production.
If you want something that will be thoroughly checked over to make sure there are no issues, you will have to pay a company to make a device just for you. That wont be cheap, your couple hundred dollar smartphone just into a couple hundred million dollar smartphone.
Thankfully, when there are genuine defects most companies take responsibility and give you a new one (though again, this will not be perfect with mass production). Companies will have different policies. Also, service reps, technicians, and the myriad of others involved in the transaction will vary (in competence, attitude, etc.).
But, if you have a screen flicker on this phone I do not see why a claim would be denied.

N5 OTA received?

I was hoping to just start a thread for those of us who are deciding to just wait for the OTA update. Have anyone actually received it yet? If so please post!

Im gonna wait for the OTA. I'm in the UK if it makes any odds. I flashed factory image to my nexus 7 so I've had my lollipop fix.
I dont want to do a clean install on my nexus 5. Hence why I'm gonna wait for the OTA.

garryboy said:
Im gonna wait for the OTA. I'm in the UK if it makes any odds. I flashed factory image to my nexus 7 so I've had my lollipop fix.
I dont want to do a clean install on my nexus 5. Hence why I'm gonna wait for the OTA.
Click to expand...
Click to collapse
In the past I don't think region have mattered that much when they have been sending out OTA's. I think its usually based off of production number/batch number. I could be wrong tho.
Haven't received it either.

I haven't yet and am waiting patiently. I'm in San Diego.

According to some Google engineer, the OTAs are initially sent to 1% of users. Assuming that 10 million nexus 5 have been sold till now, this puts the number of people who should've got the OTA at 100,000. But we don't have anyone reporting in an OTA. Not one person

Ananay Singh said:
According to some Google engineer, the OTAs are initially sent to 1% of users. Assuming that 10 million nexus 5 have been sold till now, this puts the number of people who should've got the OTA at 100,000. But we don't have anyone reporting in an OTA. Not one person
Click to expand...
Click to collapse
Interesting. Is that 1% initially within the first how many days? At what point do they reach 100%?

thisisdan26 said:
Interesting. Is that 1% initially within the first how many days? At what point do they reach 100%?
Click to expand...
Click to collapse
"Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure nothing looks wrong before sending it to more. Then typically it goes to 25%, 50%, 100% over the course of a week or two.
What the percentages mean is that when your device checks in, it has a 1% chance (for example) of being offered the OTA. If it doesn't (randomly) get an offer, it will never get an offer until the next batch.
IOW, once your device checks in and gets turned down, that's it until the next batch. Mashing on the "check for updates" button just causes your device to check in again, and get automatically turned down again. Think about how that makes your device feel! WON'T SOMEONE PLEASE THINK OF THE PHONES?!
That said, once the new batch does start, hitting that button does give you a new roll of the dice -- but once. Since devices usually only check in for system updates every 24 hours (I think? Certainly on a many-hours basis) this can get you your shot sooner than it would happen on its own.
So, mash away. Just be patient, and mashing on it more often than once or twice a day isn't going to gain you anything.
Edit: also, keep in mind that this isn't first-come/first-served. You're not racing other devices to get your slot in the current batch, or something."
http://www.reddit.com/r/Android/comments/1r1dz4/44_kitkat_has_started_rolling_out_on_the_n4/cdiwt6f

thisisdan26 said:
Interesting. Is that 1% initially within the first how many days? At what point do they reach 100%?
Click to expand...
Click to collapse
They send OTAs to 1% of the user base for the first 24-48 hours. If everything is fine, that is, there is no major bug and the performance is good, they roll it out to the next 25%. 2-3 days later they send it out to another 25%. 100% roll out is completed by the end of the week or 10 days if they're late.

http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327

Ananay Singh said:
They send OTAs to 1% of the user base for the first 24-48 hours. If everything is fine, that is, there is no major bug and the performance is good, they roll it out to the next 25%. 2-3 days later they send it out to another 25%. 100% roll out is completed by the end of the week or 10 days if they're late.
Click to expand...
Click to collapse
BTW this 1% of user base is region based ?

Ananay Singh said:
According to some Google engineer, the OTAs are initially sent to 1% of users. Assuming that 10 million nexus 5 have been sold till now, this puts the number of people who should've got the OTA at 100,000. But we don't have anyone reporting in an OTA. Not one person
Click to expand...
Click to collapse
I haven't seen one person get it either.

pearleye said:
BTW this 1% of user base is region based ?
Click to expand...
Click to collapse
Not region based

You can force ota update with Nexus Update Checker.

maslokm said:
You can force ota update with Nexus Update Checker.
Click to expand...
Click to collapse
how does that work?

As I read the app information for Nexus Checker, it seems that it lets you know when someone with a similar device running the app has received their OTA. I don't believe it forces any update.

Stigga said:
how does that work?
Click to expand...
Click to collapse
Try it. It will force download ota and reboot to recovery and install it. I'm using it for year in my n7 and n5. I don't like waiting [emoji1]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I just manually updated the ota on my phone. http://m.androidcentral.com/update-your-nexus-lollipop-using-ota-packages
Sent from my iPhone using Tapatalk

Same followed Sandman's procedure and sideloaded lollipop via adb. Saves waiting around for update.

Still kind of weird that no one has seen or heard of an ota update

Suppose its only 1% of the devices that received the first OTA. Not a lot