https://groups.google.com/forum/?fromgroups=#!topic/android-platform/EMjbexyJPh4
Read that, really read it, and then maybe if you guys can open your mind for a few brief moments you'll realize that the
Sprint CDMA Nexus S 4G was also removed from Google's AOSP source support.
Hur dur it's all Verizon's fault, yet the Sprint Nexus lost AOSP support too..... I guess it's still all Verizon's fault, at least in a world without logic.
There are 4 binaries for the RIL, any RIL. 3 of them are in the open source code. The 4th is vendor specific. This is your hold up. Hey guess what? The only 2 that lost AOSP support were CDMA networks. How about you open your mind a bit
Are you kidding me? I spelled it out for you and you still are trolling me?
Here:
A SPRINT PHONE.
A !@#$ING SPRINT PHONE.
WAS REMOVED FROM THE AOSP SOURCE FOR THE SAME REASON A VERIZON PHONE WAS.
Are you seriously ignorant or are you just trolling me? Please tell me you're just trolling me, because I'll admit it's working. I refuse to believe such blind ignorance could be real.
See above. No trolling on my part, i just cannot believe how thick you are being.
Not getting any apologies from me, I stand by what I said (and researched.)
All the information that was needed was in that XDA Samsung quote. All your dissecting and nit picking doesn't change the fact that the original point still stands: Verizon does not make the ROM's. They do not cook the RUU's. HTC (and the other OEM's) do. Verizon uses CDMA. CDMA is a PITA for open source. At the basic level each chipset is different, and it's up to the OEM to come up with drivers for it. End of story.
I am pretty sure I explained the process. but here goes again.
Google puts out AOSP. This will not run on Verizon, pretty much at all in this state.
HTC grabs the source from up there and integrates sense, the drivers for everything and a few other goodies. In this state, It might boot, but I doubt it
Verizon then takes it in adds in bloatware (I would even mention games, but data widget, verizon backup assistant and crap like that.)
They also add in the RIL and make sure it can run on their network without issues.
Anyone can compile a ROM with the right binaries.
Let me appeal to your common sense here for a minute. Verizon is not going to share proprietary information (their part of the RIL). The are also not going to allow an unapproved, experimental device on the network. They have a walled off network to experiment on.
Furthermore, Why would HTC devote Time, Money, Resources, and things like that for things that Verizon gets paid for?
Here I know that Google is failing on you big time but I will show you how it is:
Android Is As Open As The Clenched Fist I'd Like To Punch The Carriers With | TechCrunch
Please if you are going to try to prove something, do not use a post on a forum to try, get a real article.
Verizon controls the radio software. We have confirmation of that from Google and the Android team. There has been no nitpicking.
Verizon has far more influence on the software than you are saying they do. They are the reason for the delay, not HTC.
Sent from my SCH-I535 using Tapatalk 2
Just in case you missed it last time:
Android Is As Open As The Clenched Fist I'd Like To Punch The Carriers With | TechCrunch