yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] oldblue910:
Well considering HTC has delivered the GPE one's update to Google, the GPE GS4 can't be that far behind. I bet we'll have the update either this week or next.
[Galaxy S 4 General] WhiteSRT69:
seeing that my Nexus 4 still hasnt gotten the official OTA, i really doubt this. im aiming for early to mid December
[Galaxy S 4 General] oldblue910:
Well Google had already released the factory images for the N4. They never do that unless an OTA is imminent.
[Galaxy S 4 General] iamnotkurtcobain:
No GPE 4.4 in sight... :(

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 General] SGSIV:
im waiting too
[Galaxy S 4 General] :
Samsung opensource post android 4.4 kitkat source.

I9505GUEUBMKG

http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-I9505G

:p:p:p:p:p

---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------

I9505GUEUBMKG very soon!!!!!!!!!

http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-I9505G

:highfive::highfive::highfive::highfive::highfive:
[Galaxy S 4 General] oldblue910:
AWWWWWW YEAH!!!! That means OTA this week most likely!
[Galaxy S 4 General] MariuxReloaded:
Even if the first firmwares were rejected twice by Google, today HTC has updated its two GPE devices to Lollipop 5.0.1! Still nothing from Samsung! Why? Because they've decided to update first their flagship, the S5, yesterday, instead of the S4 GPE, which doesn't need changes, since it's vanilla Android!

Now it's sure: this has been the second and last Samsung device I've bought, then I'll move to Nexus! -_-"

EDIT:

The Motorola Moto X Google Play Edition has been updated to Lollipop on November 25th, so the only GPE device to be updated is the S4! Grrrr!
[Galaxy S 4 General] hermit17:
Thanks for this!
[Galaxy S 4 General] SamuriHL:
The X isn't even a gpe. It's a pure edition and controlled strictly by moto. I point this out because it beat both the gpe devices and Nexus. Go, moto. Lol. I still don't see a new kernel source posted for the s4 gpe so my hope of having it today seems to be dashed. Very frustrating.
[Galaxy S 4 General] MariuxReloaded:
Oh, now I understand why it's called "Pure Edition", thanks Samuri ;)

Exactly! Samsung wants to be always the "prima donna", so, definitely it will never start Lollipop rollout for the S4 GPE in the same day of HTC! Another black mark for Samsung! -_-"
[Galaxy S 4 General] SamuriHL:
To be fair my nx6 doesn't have 5.0.1 yet, either. Google really blew this 5.x launch.
[Galaxy S 4 General] romdroid:
I'm doing the opposite, I'm upgrading to the Note 4 soon. Nexus 6 isn't the best bang for the same buck righ tnow.
[Galaxy S 4 General] MariuxReloaded:
Yeah, I know. Google has started Android 5.0.1 rollout only for Nexus wifi versions for now.

I think HTC has updated its two GPE devices directly to the last Android version to ask for HTC GPE users' forgiveness, because, unlike Samsung, they are professional and they care about their users -_-"
[Galaxy S 4 General] -sandro-:
I don't think waiting for a few more days it's the end of the world guys, the HTC ONE M7 got it today.
[Galaxy S 4 General] MariuxReloaded:
That's not a problem, Sandro. We're waiting Android Lollipop since June, so it's not terrible if we wait a few more days.

The real problem is Samsung's iniquity: if you decide to create a GPE device, you are obliged to update it before all your other devices, because that's the rule for GPE devices.

All other GPE manufactures have always followed this Google law, why Samsung does not this time? Because it has given preminence to the S5, which is not a GPE device.

If this delay was due to technical problems, Samsung was justified, but its choice to update first its flagship shows a complete lack of interest for its older users, and that's not fair
[Galaxy S 4 General] petrus764:
We've been officially waiting for a Lollipop release since the code was pushed to AOSP little over a month ago.

No, you are not. You have obliged to produce a version built upon AOSP, not touchwiz and push updates within the required 18 months following release as Samsung is a member of the Open Handset Alliance. Manufacturers that are not OHA memebers are not obliged to update their handsets at all. Nowhere does it state that GPE devices has to be updated first, it is presumed since they in theory need less modifications, but as we've seen from numerous leaks, Samsung was toying with Lollipop for the S5 long before the code was pushed to AOSP.

As stated, there is no google law requering GPE devices to be updated first. Motorola updated their Moto X in just a few days and the 2013 version after a few weeks, but the Moto G GPE edition has not been updated with Lollipop yet. So the S4 is not the only GPE device lacking Lollipop.

Are you 13 years old? Of course they prioritize current flagship devices, as does every other OEM out there, including Google. The only company that updates all their devices at once is Apple.

Wow, stop *****ing.
[Galaxy S 4 General] SamuriHL:
Small correction to that, the Moto X 2013 has not, in fact, been updated to 5.x yet. My son is still waiting after I gave him my Moto X GSM DE.
[Galaxy S 4 General] petrus764:
edit: Nvm, mixed things up.
[Galaxy S 4 General] SamuriHL:
The 2014 X Pure Edition and VZW variants are already out of soak and are rocking 5.0. The Pure Edition had one leak, one OTA, and a NEW OTA just pushed this week. The 2013 X in all varieties is MIA for updates. I suspect coming soon, but, no one knows when. The 2013 G just went to soak for 5.0. While I'm not whining by any means as I simply don't care really, it is a bit disconcerting that there is no sign at all of the S4 GPE update at this point. Typically it's been no longer than 15 days after Nexus devices. That would technically have been yesterday or today since 5.0 was released for Nexus devices. For the record I'm laying the blame for this mess at the feet of Google, not Samsung. 5.0.1 is nowhere to be seen on the cell radio Nexus devices. What worries me the most is the idea that carriers now have some semblance of control over OTA updates for Nexus AND GPE devices. Could that be the reason for the delay? Don't know....only conjecture here. At this point, however, I suspect we'll be seeing 5.0.1 rather than 5.0. The question is when that'll happen. It's only been a few days since 5.0.1 was released on wifi only Nexus devices. If that reset the clock, well, it could be another week or two before we see the OTA. We simply don't know.
[Galaxy S 4 General] MariuxReloaded:
Hi guys!

I tweeted again with Samsung Mobile US about a possible date for Lollipop update on the S4 and they've told me this:

"Thanks for checking in, Mario! Please reach out to your carrier for more info. Release timing varies by carrier."

Now, my question is: is it possible to receive news form the carriers (AT&T and T-Mobile, if I remember well)?

Of course, I ask it to those of you who are their customers in the US ;)
[Galaxy S 4 General] SamuriHL:
You talked to a moron. LOL. GPE devices aren't sold by carriers. While they appear to now be able to assert control over WHEN the update is pushed out, Samsung has not gotten the update ready by virtue of them not posting the kernel source. Asking the carrier isn't going to do anything. This only proves that the idiots they have answering questions at Samsung are still not aware that they have a GPE or what that even means. The answer you got is for carrier branded devices.
[Galaxy S 4 General] MariuxReloaded:
That's exactly what I thought, but I wanted to ask it to you to be sure. I didn't expect anything different from Samsung Mobile US -_-"
[Galaxy S 4 General] SamuriHL:
That's what's irritated me about this phone from the beginning. Samsung pretends it doesn't exist. When people asked them for ODIN images over a year ago, they said use Kies. When it was said that the S4 GPE wasn't supported by Kies, they were told to ask their carrier about it. Really? Just lunacy IMO.
[Galaxy S 4 General] ugach maaz:
(Noob)

Just curious.. When samsung does post the gpe kernel source, is it possible to build the gpe rom from the stock nexus rom and samsung's kernel source?
[Galaxy S 4 General] SamuriHL:
Not fully, no. It doesn't include some of the drivers necessary. It's possible to build the kernel, though.
[Galaxy S 4 General] jaykresge:
I just wanted to post clarification on this. Carriers still only have the ability to delay updates for devices that are branded by them, or contractually sold by them. This recently affected the Nexus program, specifically, the Nexus 6 (and LTE tablet variants). It was a concession by Google.

GPE devices are still not sold by any American carriers, and as such, there's no contract governing them. The updates are pushed out when ready, regardless of what any carrier would want. However, I suspect future GPE/Silver devices, if either program should continue, will be offered partially by carriers and then subject to similar rules as the Nexus 6. So, I'm enjoying it while it lasts.
[Galaxy S 4 General] SamuriHL:
They actually do specify that GPE's are affected, as well. The way it works is by SIM you have installed, not where you bought it.

http://www.androidpolice.com/2014/1...ay-waits-may-be-longer-based-on-your-carrier/
[Galaxy S 4 General] MariuxReloaded:
I read that news, indeed I asked to Samsung Mobile US if there was a release date of Lollipop for the S4 GPE even for this reason.

My question is: is it possible to download the new firmware from the Open Source Release Center and then flash it on your device?

Because this is definitely paradoxical: I've bought a device which is famous for being updated quickly and now I have to wait for my carrier to upgrade it???
[Galaxy S 4 General] SamuriHL:
No no. That's not how this works. The language that Google put on the update page says that carriers may delay an ota for certification. They do this based on the sim you have installed. So if att decides they need to look at an ota for whatever reason, those devices with an att sim may not get it pushed to them until att certifies it. Mine is currently no carrier as it has no sim. Also sideloading will work. Once the update name is found we can provide a direct link to it from Google for you to sideload. It's unlikely that the carriers have anything to do with our current situation.
[Galaxy S 4 General] Spacemonkie4207:
Samsung is really taking its time with this one. I remember KitKat was available rather quickly.
[Galaxy S 4 General] MariuxReloaded:
I hope it so because, as SpaceMonkie said, Samsung is driving us to an early grave -_-"
[Galaxy S 4 General] SamuriHL:
I don't think Samsung cares all that much. The S4 GPE was not a wildly successful device and there isn't 10 million of them out there screaming for an update. They're focused on their new precious toys. Like the S5 that already has TW builds running for it. Why do they care about something that isn't branded with their amazeball UI? LOL. Patience. It'll come. When is an open question.
[Galaxy S 4 General] MariuxReloaded:
That's right and, I'm monotonous, I know, but this is my second and last Samsung device.

This applies to tablets, too: the Galaxy Note 8.0 has been the first and last Samsung tablet I've bought
[Galaxy S 4 General] johannes140:
Okay guys, i understand your/our frustration with this update and Samsungs way of doing things in general, but can we refrain from spamming this thread with a discussion about an update that is not there yet? Please only post 'valid' information or the update, when it actually arrives. This keeps people like me from reappearing in this thread, hoping for 'good' news, just to be disappointed again. Thanks...
[Galaxy S 4 General] jaykresge:
Did you just read the title, or the entire article? The article implies that this is likely just a CYA thing for Google going forward.

But there's an easy way to test this. Lollipop went out for the M7/M8 GPE last week. Ask around and see if there was a trend of update delays based on carriers (Hint: so far it's been carrier agnostic).
[Galaxy S 4 General] SamuriHL:
Yes I read the article. And I've read accounts from non-US carriers on how updates work for them. But I'm not going to argue "interpretation" with you about what it says on Google's update policy page. What I am going to do, however, is not post again in this thread until the OTA is released, as requested.
[Galaxy S 4 General] DJ_Jedi:
Guys, SamMobile already showed 2 builds of GPe Lollipop on S4, the latest one it was still buggy so we may have to wait some more but i will arrive, im sure they wont throw all the work and they have an agreement with Google, so they have to update until Google says so.
[Galaxy S 4 General] jaykresge:
If you were offended by my post, then I apologize. That was not my intent. I don't think that there is any need for either of us to come across as defensive.

This website/forum is a valuable resource for many people. No one person knows everything. There's many things that you know that I don't, and vice versa. It's when we pool our knowledge that the community benefits.

That said, I'll try to clarify my post better. Google's policy is appears to be a CYA. Google absolutely will be allowing carriers to test and delay updates as needed. But this appears to be primarily aimed at phones sold by carriers. It was a major concession for Google just to get the Nexus 6 on as many carriers as possible. Over time we'll see if updates are being delayed by individual carriers. It's unknown at this time if it's a per-carrier thing (IE, Nexus 6 on AT&T gets Android 5.x ahead of the Verizon model), or if Google is going to wholesale hold up a model's update until that model is vested by all participating carriers (like Apple does with iOS updates). If updates have been delayed to this point, the latter is the most likely scenario as the GPE devices that have received 5.0/5.0.1 have not had any noticeable delays between carriers.

If it were sim based and an individual carrier could delay an update, there's nothing stopping a user from removing the sim to get the OTA (though a factory reset may be in order, or other intermediate steps). If getting around an OTA blockade was so easy, I don't think that an overbearing carrier would like that.

In time, we'll see. I was merely pointing out that you were making assumptions based on things that we don't have complete information on, and you came across as presenting those assumptions as fact. And if I came across as doing the same on the other end, then I apologize. Both our posts were speculative and need to be highlighted as such at this time.
[Galaxy S 4 General] SamuriHL:
I think you misread my posts as saying carriers were GOING TO delay OTA updates. That is not the claim I made nor my intention to portray. All I was saying is that the carriers have the option to delay updates on both Nexus and GPE devices based on the updated language on Google's update page. Whether they choose to exercise it or not, I make no claim on that one. Carriers outside the US HAVE exercised that option so we know how it will theoretically work. They've said that pulling the SIM on a carrier that delays the update allows them to get it anyway. ;) So there's really nothing to fear here.
[Galaxy S 4 General] SamuriHL:
I'll see if I can dig it up again. It was the comments on one of the articles talking about the change and some international people chimed in saying that's been the case for them for several Nexus phones already and that removing the sim allowed the update to install. I'll see if I can find the link tomorrow.

It's from the article I posted before. Scroll down and look at the comments from Australia.
[Galaxy S 4 General] MariuxReloaded:
Moto G Google Play Edition updated to Lollipop 5.0.1!

http://www.androidpolice.com/2014/1...-google-play-edition-getting-lollipop-update/

As usual, the S4 GPE will be the last device and we still don't know when it will be updated...
[Galaxy S 4 General] MariuxReloaded:
Hey guys, I asked again to Samsung Mobile USA on Facebook for further information about the update, telling that it all depends by Samsung and not by the carriers, but the answer has arrived by Samsung Support USA and I think I can't see their answers, because I don't live in the US. So, can someone of you see what did they say? Thanks ;)

https://www.facebook.com/SamsungMob...al_comments=3&ref=notif&notif_t=share_comment
[Galaxy S 4 General] furbyx92:
I believe that they answered the question and then they delete comment, so you get phantom notification.
[Galaxy S 4 General] MariuxReloaded:
Oh ok, so that's not due to different proxies between Europe and the US, thanks ;) I don't understand why they've deleted their answer -_-"

EDIT:

Question completely deleted by Samsung Mobile USA staff, maybe because it was receiving too much Likes by angry users. Congratulations to Samsung for its censorship policy!
[Galaxy S 4 General] jaykresge:
http://ausdroid.net/2014/12/04/yes-telstra-is-blocking-your-nexus-updates/

Here we go. Seems to be update specific and not OS specific. So, in this case (I want to clarify, I'm speculating here), it seems that Telstra has not certified the Lollipop update. So, any device with an available Lollipop update would not see the update as available until you either A) replaced the sim with a carrier sim that isn't blocking the OTA, or B) remove sim, factory reset, update on wifi, and then replace sim.

So they may be carte blanche blocking Lollipop updates, and not just Nexus 4/5/6/whatever updates. Again, speculating. I haven't looked for an update to this, but an easy way to confirm would be to find out once Telstra certifies Lollipop if it rolls out for all affected devices, or of they certify by device.

As always, thanks for the info that you provide, and hopefully with all parties involved, we can find out the EXACT process used to better understand it.
[Galaxy S 4 General] SamuriHL:
Thanks for finding that as it elaborates more than what I had read from end users. It's a bit troubling that carriers can do these things on devices they didn't sell. Anyway, I don't want to keep derailing this topic but the issue of OTA's and carriers being able to block them is relevant to everyone here. I don't personally think that's the case with the S4 GPE update as they haven't even published the kernel source....still. The fact that their S5 in other countries has beaten the S4 GPE to the Lollipop parade speaks volumes to me. I will continue to support the S4 GPE community while I can, but, I'm so glad I got a new device.
[Galaxy S 4 General] jaykresge:
I'm still not fully convinced. It still only affects models sold by the carrier (includes phones of that model sold by other carriers, once the carrier's sim is inserted). I'm NOT saying that carriers CAN'T block a GPE firmware update (and if/when I said that, I was wrong), just that they likely won't. Telstra isn't going to obtain models of limited volume phones that they don't sell just to test firmware. Just due to this reason alone, current GPE models should be free of carrier OTA blocking, which was the primary point that I tried to convey earlier.

That GPEs were included in Google's CYA was enough to convince me that the GPE program may go forward and even expand to carriers, which would then cause those carriers to want to test the relevant firmware.

Am I making more sense now?

EDIT: Typo, bolded correct as it completely changed the meaning.
[Galaxy S 4 General] SamuriHL:
I personally feel the gpe program is dead but time will tell. But yes I get your point.
[Galaxy S 4 General] peshellas:
i chated with google for more than an hour yesterday, and they said carriers can block updates on certain regions even on gpe devices, but i told them i use my phone many times without a sim(carrier) and they told me then its up to google or the manufacturer to push the ota. so thats the official answer.
[Galaxy S 4 General] muniz_ri:
The 5.0 ota is rolling out now. Check your devices.: http://xdaforums.com/showthread.php?p=57457612
[Galaxy S 4 General] jaykresge:
The fact that you made this post tells me that you didn't understand my point. Don't take that as an insult though. It was likely a failure on my part to convey it. Let me try again (see bolded correction).

-Google pushes OTA to "random phone model GPE"

-In order for the carrier to block the OTA to "random phone model GPE," they must know the model number, build number, and if they're going to block it, it's because they want to test it.

-How likely is it that a carrier will obtain a "random phone model GPE" that was limited to one country, in a very limited number of sales, just to test it for that one customer on their network that uses it?

Can they block it Absolutely. Will they? Only if it's worth their time, and current GPE models aren't worth anyone's time, not even a North American carrier's. So the point you just made does not disprove mine. It reinforces what I said.
[Galaxy S 4 General] oldblue910:
If anyone gets the update, please snag the filename before you update. Thanks!
[Galaxy S 4 General] SamuriHL:
I just checked mine and it's not pushing to me yet, so, it looks like I'll need to sideload it and then I can create the ODIN images.
[Galaxy S 4 General] Danvdh:
https://mega.co.nz/#!CZt0wLSB!VwJ6NkMjuLKQWfVZXn5Ow79XSkoG8q0kqICvuThMCNk
[Galaxy S 4 General] SamuriHL:
http://android.clients.google.com/p...USER_I9505G_XAR_UCNF3_to_UDNL3_Update_FWD.zip
[Galaxy S 4 General] oldblue910:
Thank you! I'll update the first post. Is it 5.0 or 5.0.1? What's the build number?
[Galaxy S 4 General] SamuriHL:
I have no idea. Failed to sideload. Looks like root messed with something on system so this is going to be problematic at best to get this to install.

/system/bin/ddexe

Know anything about this file?
[Galaxy S 4 General] furbyx92:
It's 5.0.0
[Galaxy S 4 General] oldblue910:
Is the build number LRX21P?
[Galaxy S 4 General] furbyx92:
I don't install it yet, but it says 5.0.0 update.
[Galaxy S 4 General] oldblue910:
OK once you install it, could you please let me know the build number? Just want to make sure I'm correct in the first post. :)
[Galaxy S 4 General] furbyx92:
Yeah, of course but i have to wait to be in home, maybe in a 4 or 5 hours.
[Galaxy S 4 General] oldblue910:
Sounds like busybox might have overwritten it. :/
[Galaxy S 4 General] SamuriHL:
This could present a problem. We shall see.

---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------

Yea this ain't working even after restoring my previous odin image. This is very very bad.
[Galaxy S 4 General] oldblue910:
Maybe go back to 4.4.3 or 4.4.2, then OTA manually to each step up?
[Galaxy S 4 General] SamuriHL:
Maybe. This is going to take a significant amount of work. SIGH.
[Galaxy S 4 General] oldblue910:
That sucks, man. Sorry. :/
[Galaxy S 4 General] SamuriHL:
Yea, this is definitely not good. We may have to have someone on stock 4.4.4 NF3 that's not rooted help us because those of us who ARE rooted, are completely screwed. Any volunteers? It's a lengthy process and will be a royal pain in the ass. But it will get those of us who are rooted back up and running.
[Galaxy S 4 General] Danvdh:
Get that Odin out ;)
[Galaxy S 4 General] oldblue910:
[MENTION=4830253]Danvdh[/MENTION] Did the OTA install successfully for you? Do you happen to know the build number?
[Galaxy S 4 General] muniz_ri:
Tell me what you need and I will try to help already pulled system dump from my m919: http://xdaforums.com/showthread.php?p=57462229
[Galaxy S 4 General] SamuriHL:
That unfortunately won't help me. I'm working on it, but, essentially if I can't get this to work for whatever reason, I'm going to need a clean system partition with no root pulled from an unlocked, but unrooted, S4 GPE with 4.4.4 NF3. And yes, it's possible.

BUT, alas, that won't be necessary for anyone but me as it's now installing. No one wants to ask as this process was a *****. Can't promise ODIN images tonight as it's late here, but, at least by tomorrow. And it will be my first non-rooted ODIN image as I don't want to deal with this nonsense again when 5.0.1 comes.
[Galaxy S 4 General] oldblue910:
Thanks for that. Build is LRX21P