Develop Bugs

Google pulls support for LTE Galaxy Nexus?

http://www.droid-life.com/2012/02/0...ons-lte-galaxy-nexus-to-be-a-developer-phone/
I'm not sure whether this is legit...or whether its just a mistake..LETS HOPE ITS JUST A MISTAKE OK GUISE?
Seriously though, we've been through enough with this phone

Yeah fingers crossed this isn't true...
Sent from my Gummy Nexus

If this is true, I'm going to be seriously pissed. I gave up an unlimited data plan at AT&T to get the GN because I wanted a phone that should be future-proof with respect to OS updates for 18-24 months.
I'm still within my 14 days with Verizon. I hope we get this straightened out before my return period is up...

Seems pretty clear. It's a bit too official in too many places consistently to be a "mistake".
Verizon pushed them too far, and took away too many things for Google to consider it a Nexus reference platform.
---------- Post added at 12:52 PM ---------- Previous post was at 12:51 PM ----------
ssmug said:
If this is true, I'm going to be seriously pissed. I gave up an unlimited data plan at AT&T to get the GN because I wanted a phone that should be future-proof with respect to OS updates for 18-24 months.
I'm still within my 14 days with Verizon. I hope we get this straightened out before my return period is up...
Click to expand...
Click to collapse
You could've kept your unlimited plan and bought unlocked GSM... Verizon wasn't your only option lol.

Seriously, this is a lot of uproar about nothing IMO.
The page stating CDMA devices aren't supported is for building AOSP builds for target devices. It has nothing to do with OTA updates.
You'll notice another Nexus CDMA device missing, the Nexus S 4G. Guess where it gets its updates from and always has (it's not Sprint)?

krohnjw said:
Seriously, this is a lot of uproar about nothing IMO.
The page stating CDMA devices aren't supported is for building AOSP builds for target devices. It has nothing to do with OTA updates.
You'll notice another Nexus CDMA device missing, the Nexus S 4G. Guess where it gets its updates from and always has (it's not Sprint)?
Click to expand...
Click to collapse
I'm new to Android phones (but not tablets), so I don't know exactly what those listing mean, but I sure hope you're right!

ssmug said:
I'm new to Android phones (but not tablets), so I don't know exactly what those listing mean, but I sure hope you're right!
Click to expand...
Click to collapse
They are merely targets you can pass in when building a a ROM from AOSP source that configures the source for that target device automatically and the accompanying instructions for flashing the rom you've build (From source) to that device. Along with this are the required vendor binaries (blobs) to place in the build directory for the closed source libraries for specific hardware for each device.
The sensational headline does grab attention, but that page has never had anything to do with updates.

I think even if Google drops support there will be lots of mods like cyanogen.

DonXoB said:
I think even if Google drops support there will be lots of mods like cyanogen.
Click to expand...
Click to collapse
Forgive me if this is a naive question, but would they be able to update the OS from the GSM updates?

I think Google means to pull the LTE radios, it seems like VZW to be concerned about those being OS'ed for security reason...hmmm

martonikaj said:
You could've kept your unlimited plan and bought unlocked GSM... Verizon wasn't your only option lol.
Click to expand...
Click to collapse
That is what I did. Best $700 I've ever spent!

krohnjw said:
They are merely targets you can pass in when building a a ROM from AOSP source that configures the source for that target device automatically and the accompanying instructions for flashing the rom you've build (From source) to that device. Along with this are the required vendor binaries (blobs) to place in the build directory for the closed source libraries for specific hardware for each device.
The sensational headline does grab attention, but that page has never had anything to do with updates.
Click to expand...
Click to collapse
that's worse. So there won't be devs aosp built on this phone anymore ?
Sent from my Galaxy Nexus using Tapatalk

Verizon must have really pissed off Google.

martonikaj said:
You could've kept your unlimited plan and bought unlocked GSM... Verizon wasn't your only option lol.
Click to expand...
Click to collapse
I knew someone would say that! I don't use that much data (although I'm not in an LTE area, but I am near one), and if I did have LTE, I don't really stream or tether, so it wouldn't be too big a deal. (And my company gets a 25% discount at Verizon and 5 GB for the price of 2 GB.)
Still hurt to leave it, especially since I got the GN specifically for what I thought would be guaranteed OS support...
I still have until Tuesday to return it and go back, though...

Petition to have CDMA Galaxy Nexus supported again by AOSP

Ok first off I'm not good with drawing up papers or writing letters, but I think that its bull**** that the CDMA variant of the GN has been dropped by AOSP due to the closed source of some of the drivers I am guessing is used for the LTE radio that since I'm on Sprint I'm not even able to turn on yet anyway. Also isn't this what some of you developers bought the phone for? Or I should say isn't this what you want. I just dont think its fair for Sprint/Verizon to sell a developer phone with closed source software I think that this phone should be supported or maybe we the consumer should be a little more mindful on what we financially support from our carriers and Google. If I dont have all of my facts together on this please enlighten me so I can get it together, but if you feel like I do lets get something in the carriers and Googles hands about this.

Who do you plan on petitioning?
By the way, CDMA is closed source and Google has no license to redistribute the binaries.

Good luck. CDMA is Qualcomm's baby, heavily patented and strictly licensed.

Exactly, who do you plan to petition? Google can't make the CDMA parts open-source, it's not their fault.

martonikaj said:
Exactly, who do you plan to petition? Google can't make the CDMA parts open-source, it's not their fault.
Click to expand...
Click to collapse
On a side note and to be fair, GSM parts are closed source too. Google just has a license to redistribute.

In reality it doesn't matter all that much. It's a developer phone and the support behind it is endless on that end. As long as google releases the images for GSM and the developers can use the source as a base for the roms on our phones I don't see it as a major concern. The only thing we really rely on verizon for are the radio updates which can be pulled from verizon's updates and installed via recovery anyway. I could be wrong but my rom is based on the GSM 404 image and it works great and I don't think they'll update it for the verizon 404 since the only big difference seems to be the radios.

yeah I get that my thing is that we can be heard if we make some noise but thats what I was getting at I was wanting to learn more about why support stopped and maybe is it a possiblity of getting something going to start a petition. I dont want to take Qualcomm's baby I just want to be able to baby sit every now and then?

utcu said:
In reality it doesn't matter all that much. It's a developer phone and the support behind it is endless on that end. As long as google releases the images for GSM and the developers can use the source from that to port it to our phones I don't see it as a major concern. The only thing we really rely on verizon for are the radio updates which can be pulled from verizon's updates and installed via recovery anyway. I could be wrong but my rom is based on the GSM 404 image and it works great and I don't think they'll update it for the verizon 404 since the only big difference seems to be the radios.
Click to expand...
Click to collapse
Er...we don't port GSM anything to Verizon.

adrynalyne said:
Er...we don't port GSM anything to Verizon.
Click to expand...
Click to collapse
You know what I meant. lol. As long as they have the GSM image to use as a base for the rom. I'll edit my post to make more sense.

jakdillard said:
yeah I get that my thing is that we can be heard if we make some noise but thats what I was getting at I was wanting to learn more about why support stopped and maybe is it a possiblity of getting something going to start a petition. I dont want to take Qualcomm's baby I just want to be able to baby sit every now and then?
Click to expand...
Click to collapse
Support didn't stop. Google still provides the factory images. In reality, nothing has changed. Being in AOSP doesn't mean updates still won't have to be approved. Even ROM developers haven't been stopped from creating ROMs. I'm not sure what you expect will change if they reversed their decision.

utcu said:
You know what I meant. lol. As long as they have the GSM image to use as a base for the rom. I'll edit my post to make more sense.
Click to expand...
Click to collapse
I don't know of any dev doing such a thing. They build from AOSP.
You see, the cdma code is still there. Just the proprietaries are not complete.

bozzykid said:
Support didn't stop. Google still provides the factory images. In reality, nothing has changed. Being in AOSP doesn't mean updates still won't have to be approved. Even ROM developers haven't been stopped from creating ROMs. I'm not sure what you expect will change if they reversed their decision.
Click to expand...
Click to collapse
When I say support I mean building from source I'm know they will continue to update the phone its just that now I actually like android since ICS and want to develop for it more but I just hate limitations ..... the last time I fooled with a 'droid phone it was the EVO 4G and it made me hate android and roll with a IPhone4 but fruity phones are boring and hyped up.

Why does it matter? We can build Sprint from AOSP.

adrynalyne said:
Why does it matter? We can build Sprint from AOSP.
Click to expand...
Click to collapse
Can we .... ? didn't know that please go on .....

The code is there. You just have to flesh out the device tree yourself, and create your own vendor with proprietaries pulled from your device.

jakdillard said:
Can we .... ? didn't know that please go on .....
Click to expand...
Click to collapse
You can pull the closed source drivers strait from the phone and build cm9 ,aosp, aokp whatever you want
Sent from my Galaxy Nexus using Tapatalk 2

adrynalyne said:
The code is there. You just have to flesh out the device tree yourself, and create your own vendor with proprietaries pulled from your device.
Click to expand...
Click to collapse
Ok. Let's try to explain this differently. AOSP for the CDMA Nexus exists. You can pull it, compile it, etc...HOWEVER certain "binaries" (drivers,blobs, radios. Call them what you please.) Aren't included. This isn't a problem. We have most of these anyway. They are included in OTA's and factory images. Google is no longer providing factory images so we have to pull them out of OTAs or use older ones. There really is no issue here and I'm certain Google is fighting for this to change.
Sent from my Galaxy Nexus using XDA

Google is still providing factory images for the CDMA Nexus devices. They released factory images for the Sprint Nexus S about a month ago and I'm sure we will continue seeing factory images for Verizon as OTAs are released. The only one you won't see factory images for is the Sprint Galaxy Nexus since that firmware is created, managed and updated by Samsung, not Google.
Sent from my Galaxy Nexus using Tapatalk 2

Smokeey said:
Ok. Let's try to explain this differently. AOSP for the CDMA Nexus exists. You can pull it, compile it, etc...HOWEVER certain "binaries" (drivers,blobs, radios. Call them what you please.) Aren't included. This isn't a problem. We have most of these anyway. They are included in OTA's and factory images. Google is no longer providing factory images so we have to pull them out of OTAs or use older ones. There really is no issue here and I'm certain Google is fighting for this to change.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
OK I like this explanation better

oldblue910 said:
Google is still providing factory images for the CDMA Nexus devices. They released factory images for the Sprint Nexus S about a month ago and I'm sure we will continue seeing factory images for Verizon as OTAs are released. The only one you won't see factory images for is the Sprint Galaxy Nexus since that firmware is created, managed and updated by Samsung, not Google.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Are you sure that the updates are distributed by samsung for the sprint galaxy nexus. Could of sworn it was google who did that.......?

System Update IMM76Q: VZN Galaxy Nexus

I received an OTA software update with build number IMM76Q. Has anyone else received it?

Get us a logcat before installing please.

945kb...
Hmm.
Sent from my Galaxy Nexus using Tapatalk 2

Must be the gimping of the search bar

NeoMagus said:
Must be the gimping of the search bar
Click to expand...
Click to collapse
My exact thoughts!!

Yeah. 949 kb is tinyyyyy. I can't believe Verizon would be this quick about an update Google has been working on for a week and released a day or two ago! But no..... a somewhat major software revision has to take 2 months. I realize the fact that it is only a very, very small update, and it doesn't change any major software/radio stuff... but still. You know what would be cool? If verizon pushed out software updates (i.e 4.0.4, 4.1) clean at first, then follow up with a second update on the radios.

Lol nice "screenshot".

martonikaj said:
Lol nice "screenshot".
Click to expand...
Click to collapse
Next generation screenshot.

El Madhatter said:
I received an OTA software update with build number IMM76Q. Has anyone else received it?
Click to expand...
Click to collapse
Did you manage to get the file name for us yet?
If you've already installed it, the easiest way would be to look through the log files in /cache with a text viewer and look for a file name ending in .zip.
Thanks!

Wierd, even verizons support site doesn't have this update listed. http://support.verizonwireless.com/system_update/galaxynexus.html. Normally they list the update a few days before roll out on that site. Unless they really had to rush to get around the ban. Curious what's in this update, or if its real.

nbdysreal said:
Wierd, even verizons support site doesn't have this update listed. http://support.verizonwireless.com/system_update/galaxynexus.html. Normally they list the update a few days before roll out on that site. Unless they really had to rush to get around the ban. Curious what's in this update, or if its real.
Click to expand...
Click to collapse
As was mentioned, it is probably the disabling of the "local search" feature of the search bar.

martonikaj said:
Lol nice "screenshot".
Click to expand...
Click to collapse
Its the screen shot of all screen shots... Aero Shot ... comes in Jellybean lol
-Google

If anyone else gets the OTA, please post the filename here so I can update randomphantasmagoria.com. Thanks!

efrant said:
As was mentioned, it is probably the disabling of the "local search" feature of the search bar.
Click to expand...
Click to collapse
Yeah, i know thats what it probably is. Verizon just always puts out a pdf on the support sites of their phones no matter how minuscule the update is. Like one that turned off the initial 4g free tethering last year said something like "enables 4g tethering plans" or something like that. Oh you tricky VZ...

nbdysreal said:
Yeah, i know thats what it probably is. Verizon just always puts out a pdf on the support sites of their phones no matter how minuscule the update is. Like one that turned off the initial 4g free tethering last year said something like "enables 4g tethering plans" or something like that. Oh you tricky VZ...
Click to expand...
Click to collapse
Definitely very weird that VZW wouldn't have updated the support PDFs. They update those things religiously when there's an OTA.
I hope this IMM76Q update isn't another IMM30B where someone accidentally pushes it to a few devices, shuts it off, and it fades into the ether, leaving anyone who applied the update stranded.

anton2009 said:
Yeah. 949 kb is tinyyyyy. I can't believe Verizon would be this quick about an update Google has been working on for a week and released a day or two ago! But no..... a somewhat major software revision has to take 2 months. I realize the fact that it is only a very, very small update, and it doesn't change any major software/radio stuff... but still. You know what would be cool? If verizon pushed out software updates (i.e 4.0.4, 4.1) clean at first, then follow up with a second update on the radios.
Click to expand...
Click to collapse
Technically, the updates come from Google. Since this update has nothing to do with aspects that would be specific to carrier use they probably didn't involve Verizon in this one.

live4nyy said:
Technically, the updates come from Google. Since this update has nothing to do with aspects that would be specific to carrier use they probably didn't involve Verizon in this one.
Click to expand...
Click to collapse
As far as I'm aware, that's not an option. I believe VZW has to test and approve every single OTA that goes out to a phone on their network, regardless of how small or whether there is anything carrier-specific in it.
Apple is the lone exception to this rule. Verizon lets them do whatever the hell they want with the iPhone and iPad.

I spoke to a verizon tech rep this week---he said there was an update pending and suggested it was more about a radio fix. However, I'd take that with a grain of salt

oldblue910 said:
As far as I'm aware, that's not an option. I believe VZW has to test and approve every single OTA that goes out to a phone on their network, regardless of how small or whether there is anything carrier-specific in it.
Apple is the lone exception to this rule. Verizon lets them do whatever the hell they want with the iPhone and iPad.
Click to expand...
Click to collapse
That's very unfortunate then.

It's probably just an update regarding the whole patent situation

Kitkat GS3 at&t confirmed

Proof: http://1drv.ms/OJ2Bgr
PS: Read it all:good::good:

Håvi said:
Proof: http://1drv.ms/OJ2Bgr
PS: Read it all:good::good:
Click to expand...
Click to collapse
That's already known.. the problem is them keeping the release date (or estimated release date), tight-lipped.

DazTip said:
That's already known.. the problem is them keeping the release date (or estimated release date), tight-lipped.
Click to expand...
Click to collapse
Thats just to be sure if it will come:good:

Håvi said:
Thats just to be sure if it will come:good:
Click to expand...
Click to collapse
Yeah because it would be the first time they didn't follow through with what they said...

Hopeful
As much as I hope it is released for our phones, a single person who does live chats all day may not be the most rock-solid source. Any number of things could turn out to have happened, from misreading an information sheet before giving you said information to her being just plain wrong.
Thank you for posting this though, it is important that up to date information like that is made public. Its just that I'm not sure if one representative saying it is on its way is a complete confirmation.
Does anyone know how reliable these live chats usually are?

SwaggyDabbyDoo said:
As much as I hope it is released for our phones, a single person who does live chats all day may not be the most rock-solid source. Any number of things could turn out to have happened, from misreading an information sheet before giving you said information to her being just plain wrong.
Thank you for posting this though, it is important that up to date information like that is made public. Its just that I'm not sure if one representative saying it is on its way is a complete confirmation.
Does anyone know how reliable these live chats usually are?
Click to expand...
Click to collapse
Not very reliable in this case since they are not allowed to give too much information out to the public. I posted a thread after I talked to one of Samsung's live representatives and they told me that the update would come in a matter of weeks. You can check my thread out if you want.

internethuman said:
Not very reliable in this case since they are not allowed to give too much information out to the public. I posted a thread after I talked to one of Samsung's live representatives and they told me that the update would come in a matter of weeks. You can check my thread out if you want.
Click to expand...
Click to collapse
Ah yes I found that thread. Well if it was more than just one confirmation that adds too the legitimacy :good: I don't want to get my hopes up but its looking good!

I'd love for this to be true. I'm holding off on updating to a custom rom in case they push KitKat and it doesn't work after using the stock restore posted.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

My post on the rumor thread
RoryB said:
I was talking with AT&T repair regarding my phone freezing when switching from portrait to landscape since the 4.3 OTA and they told me they were not aware of a fix coming out for this, but that 4.4 will probably come out in a couple months and it may replace whatever is causing the problem. When I went to the Samsung Experience center to let them force the OTA onto my phone again to see if that would fix the issue, that tech said the same thing about 4.4 coming out, but he thought my freeze issue is hardware related.
Click to expand...
Click to collapse

AT&T official statement or it didn't happen !

From Official Samsung
Not sure if this is only US versions but this is a list of devices from the official website
www "DOT" samsung "DOT" com/us/support/faq/FAQ00059206/82024/EFC-1G6FFEGSTA[/url] :good:

Deonta23 said:
Not sure if this is only US versions but this is a list of devices from the official website
www "DOT" samsung "DOT" com/us/support/faq/FAQ00059206/82024/EFC-1G6FFEGSTA[/url] :good:
Click to expand...
Click to collapse
I just went to change my sim card to one with secure element, and ask guy at At&t store ( is said "manager" on his name tag) about kitkat for S3. He answer
We don't have any specific date, but I heard it should be at mid May.
Click to expand...
Click to collapse
.
Make sense since S5 will be release in April so they can bust sell of S5 before they let us have it KitKat on S3.

Can anyone explain what would be the advantage of an official kk rollout from AT&T?
At this point in time AOSP kk roms are fully functional, no need to hang with an ugly fat chick like touchwiz haha
Sent from my SAMSUNG-SGH-I747 using Tapatalk

I've been using kk with pwncake's Quantum ROM for so long now, that I'm not very inclined to go back to touchwiz either. It's just too late.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Until there's an official update rolled out, I won't believe it

sgloki77 said:
Can anyone explain what would be the advantage of an official kk rollout from AT&T?
At this point in time AOSP kk roms are fully functional, no need to hang with an ugly fat chick like touchwiz haha
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Kit Kat does bring down memory usage, so if you use or want some of the S applications and features that Touchwiz has, you should see better performance due to released memory.
Theoretically that is, I've been on CM11 nightlies for awhile now.

Some cant work with non stock roms...

sgloki77 said:
Can anyone explain what would be the advantage of an official kk rollout from AT&T?
At this point in time AOSP kk roms are fully functional, no need to hang with an ugly fat chick like touchwiz haha
Click to expand...
Click to collapse
xhozt said:
Some cant work with non stock roms...
Click to expand...
Click to collapse
Or, like me, simply do prefer them over AOSP ROMs
Anyway, Xposed now fills the gap of what's missing in most cases

Deonta23 said:
Not sure if this is only US versions but this is a list of devices from the official website
www "DOT" samsung "DOT" com/us/support/faq/FAQ00059206/82024/EFC-1G6FFEGSTA[/url] :good:
Click to expand...
Click to collapse
There you go !
http://www.samsung.com/us/support/faq/FAQ00059206/82024/EFC-1G6FFEGSTA

Thats nice
Its not really important since most stock TouchWiz roms are total ****, especially those from samsung.

T-Mobile Publishes Software Update Tracker Webpage

http://www.droid-life.com/2015/02/2...le-publishes-software-update-tracker-webpage/
LG G3 is not listed.

Figures... Thanks for the link though

But no LG phones are listed, so it must be unlisted for a reason other than no update coming...

Nexus 6 isn't listed either. I'm pretty sure being omitted from that list does not mean the G3 isn't getting lollipop.

I am not quite sure as to how the LG G3 Lollipop update was left off of the list, but I am happy to report it is in the T-Mobile testing phase. And our testing is going really well. I will reach out to product development and try to get it added to the list. Thank you for pointing this out.
Click to expand...
Click to collapse
Being taken care of.

Yeah that's pretty friggin depressing when our phone isn't even listen as a device on the timeline.

pypen said:
Being taken care of.
Click to expand...
Click to collapse
Where did this come from?

Jason Syn said:
Yeah that's pretty friggin depressing when our phone isn't even listen as a device on the timeline.
Click to expand...
Click to collapse
Agreed

G3 is now listed as 'Manufacturer Development'.

Why on earth is T-Mobile just now in the testing phase when every other carrier has had a release. T -mobile is the new Verizon when it comes to updates, very sad. I expected more from the uncarrier.

Maybe they are trying to fix the roaming data connectivity issues wrt IPv6. See the old threads.

jrglasson said:
Maybe they are trying to fix the roaming data connectivity issues wrt IPv6. See the old threads.
Click to expand...
Click to collapse
Could be, T-Mobile is the only carrier using IPV6 only on LTE (if I'm not mistaken). They could also have required VoLTE be working, so LG could be taking longer to make sure all this works. Still sucks that it's taking so long.

i had to move from a nexus 5 to a lg g3, what a regression when you see t-mobile slowing such updates!

I've been using a Moto X 2nd Gen. New job has the silly policy of not allowing rooted devices to access our craptastic Lotus Notes e-mail. The G3's KitKat build is unusable without root. Hoping Lollipop is better, otherwise the G3 will be finding a new home.

bedroidapp said:
i had to move from a nexus 5 to a lg g3, what a regression when you see t-mobile slowing such updates!
Click to expand...
Click to collapse
Lol
Sent from my LG-D851

havanahjoe said:
I've been using a Moto X 2nd Gen. New job has the silly policy of not allowing rooted devices to access our craptastic Lotus Notes e-mail. The G3's KitKat build is unusable without root. Hoping Lollipop is better, otherwise the G3 will be finding a new home.
Click to expand...
Click to collapse
You could use RootCloak on Lotus Notes so your work wouldn't be able to detect it.
Sent from my LG-D851 using XDA Free mobile app

prp2 said:
You could use RootCloak on Lotus Notes so your work wouldn't be able to detect it.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I tried. Didn't work. They use Airwatch and I couldn't get anything to fool it on the G3 while rooted.
But now that you pointed me to it again, I searched through the RootCloak thread and apparently there is a version of Airwatch that can be fooled. I'll have to try it and see if I can get it working on my G3. That would be awesome.

havanahjoe said:
I tried. Didn't work. They use Airwatch and I couldn't get anything to fool it on the G3 while rooted.
But now that you pointed me to it again, I searched through the RootCloak thread and apparently there is a version of Airwatch that can be fooled. I'll have to try it and see if I can get it working on my G3. That would be awesome.
Click to expand...
Click to collapse
It worked! Now I need a good Lollipop rom. Thank you!!

xlxcrossing said:
Why on earth is T-Mobile just now in the testing phase when every other carrier has had a release. T -mobile is the new Verizon when it comes to updates, very sad. I expected more from the uncarrier.
Click to expand...
Click to collapse
The answer is so simple...
There's developmental teams for each region and NOT all of them finish at the same time... The last responses shows how childish some people are. Some devices get finished on other carriers and some don't. T-Mobile isn't always the first and they are not always the last. You can say that with ANY carrier.
If manufacturers really wanted to fix this problem they should take away the carrier options they give them, and then have a single base phone so they only need to code for a single device(iPhone 6, and 6+ as an example they are all exactly the same). Of course device prices would get more expensive then people will complain how expensive they are while blaming the carrier for the prices.

Tidbits said:
The answer is so simple...
There's developmental teams for each region and NOT all of them finish at the same time... The last responses shows how childish some people are. Some devices get finished on other carriers and some don't. T-Mobile isn't always the first and they are not always the last. You can say that with ANY carrier.
If manufacturers really wanted to fix this problem they should take away the carrier options they give them, and then have a single base phone so they only need to code for a single device(iPhone 6, and 6+ as an example they are all exactly the same). Of course device prices would get more expensive then people will complain how expensive they are while blaming the carrier for the prices.
Click to expand...
Click to collapse
The fact of the matter being LG had 5.0 in hand early to mid Q4 and many carriers were putting finishing touches on their certification by the end of the year. We are now 2 months in to Q1 and every carriers' update status has surpassed ours. When you say there are different development teams for each region I assume you mean domestically which makes perfect sense but isn't that a nice way of saying "we're not ready yet". I'm not one to usually ***** about updates because it makes things less enjoyable in most cases but I'm a little blown away. When I heard LG G3 was one of the first handsets scheduled to get lollipop I thought for sure T-Mobile would shine once more. I just need to modify my definition of "soon" because in T-Mobile's dictionary the definition is a month or more.