Obviously Verizon will not carry this phone but I do see the light at the end of the tunnel....
Will the existence of a "vanilla android" ROM for the S4 give the development community a jump start? I know very little about the ROM development process but I am hoping this is the case. What do you guys think?
Sent from my Nexus 7 using Tapatalk HD
I actually think so, yes. Granted, you won't be able to just toss the same OS image on a Verizon phone, but it could potentially be great jumping-off point for AOSP devs working on the device. Having said that though, we'll just have to wait and see.
What's the point? You lose all of the features of the S4 like Airview and such.
Why not just buy a cheaper S3 and install a stock ROM?
In a way I agree, but there are a few things to consider...
1) Verizon doesn't carry "Nexus" devices (yes, they had the GNex, but that appears to be an anomaly). Users on Verizon who want a "pure Android" experience need to either install an AOSP ROM onto another device (which can be a more frustrating experience than desired), or switch carriers (not always a desired option for many).
2) Even though you do lose the TW features that drive the marketing for the Galaxy S line of devices, AOSP ROMs are still quite popular amonst the rooted crowd. It is simply what some prefer. I am not one of those people, but I certainly understand their arguments.
Having a Google image of pure Android made specifically for the S4 may allow for some great AOSP ROMs for those that prefer to go that route. Granted, differences in hardware won't make it an exact fit (the radio will have to be modified, for one), but with any luck it does provide a platform to work off of, and make the AOSP experience less buggy and more refined than previous Verizon Galaxy S phones experienced.
They are busy stuffing it with VZ bloat
Realize this comment was made tongue-in-cheek, and yeah, folks like to bash Verizon for this practice (I'm one of them), but I cannot believe that it is the "bloatware" that causes the delays in release of updates/devices when it comes to VZW. I mean, we're really just talking about adding a few apps to the OS build, which should take very long at all. What does probably cause the delays is Verizon's own QA process and even possibly internal CS training. Folks hate the delays, including me, but I understand that Verizon, having as many customers as they do, want to mitigate any potential issues
prior to release.
It's also possible that Samsung simply wasn't able to supply them with the CDMA phones in time to release at the same time as the GSM carriers -- Verizon can't sell what it doesn't have. That, however, is purely speculation on my part, I have no idea.