Samsung Galaxy S4


Recommended Posts

Doubt it as well since Samsung would then have to release Exynos source to be supported in AOSP. I guess they can still do blobs for some stuff but not sure about CPU.

SGS2 though as "bad" as it's been has actually been pretty good. It received ICS and JB (4.1.2) which is MUCH more than any other "old" phone out there (besides Nexus Devices).

I guess regarding the whole Exynos source code issue, Samsung could easily get around it by just doing a 4G version with the Snapdragon instead. I assume the Snapdragon source code is available?

For me, it felt like Samsung only put minimal effort into the updates. After all, the S2 was their real first successful smartphone with over 10 million devices sold. 4.1.2 was only pushed to the i9100 after it 4.2 had released :p. Surely their close relationship with Google would have told them to wait for the 4.2... right?

Also, correct me if I'm wrong, but didn't Sammy only release the 4.1.2 update after there was a big backlash from i9100 owners and a petition was made because the phone was still under 2 years old (April 2013) at that point? Samsung signed a deal to support a smartphone through updates for at least 2 years. Unfortunately, many OEM's (not just Samsung) haven't lived up to this promise very well!

Link to comment
Share on other sites

That is what I mean, when Google take control and update the phone directly it's fantastic. However, when the OEM takes control (and/or the carrier interferes) it becomes are nightmare! my Galaxy Nexus is perfect example of what I don't want to see happen again. Because I got my Nexus from my carrier, it is not supported by Google (Samsung support all carrier supported variants, Google wanted nothing todo with it since they know dealing with the carriers is a pain) and Samsung couldn't careless about the phone and (rumour has it) they have dropped support entirely for the phone after 4.1.2 (well in Australia they have). So if you want anything later (despite Google supported Galaxy Nexus phones running 4.2.2 with rumours of getting 4.3 as well) it's tough luck and your forced to root the phone to get an update you should be getting.

To be honest it's left a very sour taste in my mouth and almost completely put me off getting another Nexus device (adding to the frustration is seeing OEM devices getting newer versions of Android and getting them faster)...sort of destroys the experience in my humble opinion.

Do this:

http://tutorialandro.blogspot.com.au/2013/05/how-to-flash-official-android-412-to.html

Its the official ROM from Google and will get around any bull**** carrier lock they have over the updates and brings the phone to how it's supposed to be.

I have had to do this for 3 people at work who had Telstra Samsung Galaxy Nexus phones and they have 4.0.1 when jelly bean was out for over 5 months.

Nexus phones are supposed to be just that, clean and directly up datable from Google, not determined by carriers.

Link to comment
Share on other sites

I guess you are right about the snapdragon version, didn't think of that. Google prolly already has the source for the new Qualcomm CPUs anyways as they are probably in the new Nexus devices being made.

As for the GT-I9100 - AFAIK they were gonna release it anyways but people were being bitchy and wanting it ASAP. The fact that we got leaks earlier on suggest they were at least working on it from long ago but people were just impatient because their SGS2s didn't updates right away compared to newer phones that Samsung still needs to actively support :)

Link to comment
Share on other sites

I want now. Well, until I get more information and I might change my mind. If I have to get my updates through AT&T I will never get an update.

Link to comment
Share on other sites

Now if HTC One made partnered with Google to do the same, it would be so nice.

Link to comment
Share on other sites

I guess you are right about the snapdragon version, didn't think of that. Google prolly already has the source for the new Qualcomm CPUs anyways as they are probably in the new Nexus devices being made.

As for the GT-I9100 - AFAIK they were gonna release it anyways but people were being bitchy and wanting it ASAP. The fact that we got leaks earlier on suggest they were at least working on it from long ago but people were just impatient because their SGS2s didn't updates right away compared to newer phones that Samsung still needs to actively support :)

Yeah, very true it did have quite a few leaks over the dev time. Some over at XDA can be quite impatient :p

Link to comment
Share on other sites

Come on, there's no source at all on that site which means it's just link bait. Be a bit more critical people.

It was just confirmed!

Link to comment
Share on other sites

Come on, there's no source at all on that site which means it's just link bait. Be a bit more critical people.

It was recently confirmed at the Google I/O keynote. :)

Link to comment
Share on other sites

I wonder if this will sport the Exynos 5 or Crapdragon 600 rebranded S4 Pro chip. And as always, it won't obviously be sold in the rest of the world..

Link to comment
Share on other sites

Heard they are calling it a Nexus phone now to. At least what The Verge said. If so, then I may have my new upgrade in August. :) That is if it comes to Verizon as well.

Link to comment
Share on other sites

Heard they are calling it a Nexus phone now to. At least what The Verge said. If so, then I may have my new upgrade in August. :) That is if it comes to Verizon as well.

No more AOSP on Verizon! They control too much to make it work as Google intended. :(

Link to comment
Share on other sites

No more AOSP on Verizon! They control too much to make it work as Google intended. :(

So there will be no more Nexus devices on Verizon? My GNEX has always worked just fine.

Link to comment
Share on other sites

So there will be no more Nexus devices on Verizon? My GNEX has always worked just fine.

It works but if you noticed you guys took forever to get updates which "fragmented" even the Nexus line which Google doesn't want. Google doesn't have access to the radio controls for CDMA because it's only licensed to carriers (aka Verizon/Sprint). As a result they need to send the AOSP code to Verizon then V will check it out and then "tweak" it to make it work then it gets released. Those changes however doesn't get back to AOSP because only Verizon is licensed to the code.

Link to comment
Share on other sites

It works but if you noticed you guys took forever to get updates which "fragmented" even the Nexus line which Google doesn't want

Ahh, no big deal. I root.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.