Not to Cause a Panic...

Mtn_Scott

Remain Calm!
Feb 2, 2011
230
22
0
...but, after a very quick (10 minute) 10 minute search of Rootzwiki I discovered that most Verizon LTE devices (Not including the Nexus) do not have fully functioning AOSP roms. I will pretend to understand this and say the the RIL is proving to be problematic. The Charge (essentially a fascinate with LTE) does not have Data working on AOSP. The Fascinate was one of the first to have a ICS build from the Dev Community. The Dev who produced ICS for the Fassy is still not able to get it working on the Charge. This has me nervous as to our ability to Ditch TW in the future.

Desperately looking for someone to dispell my fears.
 
...yeah. It's the nature of the beast. We may or may not get AOSP. The Thunderbolt is the only non-Nexus LTE phone with AOSP. But I'd bet we do get it because of the sheer number of devs.

Surely you knew this already?
 
Oh, I did. The fear did not outweigh the desire for LTE, 2 more years of Unlimited data, and a shiny new Sammy. I am hoping that someone can assuage my fears a bit.
 
You should never expect a fully functional ROM of an OS that was never released for your phone. Not that easy for devs to get it working unfortunately.

Sent from my Galaxy Nexus
 
  • Like
Reactions: Ry and dmmarck
Yeah, there's not really a way to assuage your fears. I think there's a better than 50% chance we get AOSP, but it's not much more than 50%. It's a lot of tedious work to get the RIL working. I think our best bet is if the RIL is essentially identical across all 5 carriers, with minor differences for frequency. Fingers crossed. It should be, I would think, since it's the same chip in all 5 phones.
 
I guess the Fassy developers spoiled me.

Maybe I should clairify functioning as working data.
 
What are aosp roms? Sorry noob question haha

Sent from my DROIDX using Android Central Forums
 
Since XDA has combined forums for all the US variants and said that the rom's should be interchangeable with minor tweaks, that's a pretty good sign they intend to make it work.
 
I have a Charge and remember all the frustration with never getting AOSP. That was due to the encrypted RIL, and the fact that we had about 2 or 3 guys with any interest in bringing it that actually knew what needed to be done, and only one that was able to make any real progress (thanks jt1134!). But it's not true that the T-Bolt is the only one with working AOSP, I've been running various AOSP roms on my Razr for months now, and the other LTE Moto devices have it as well, and these are all with locked bootloaders.

Sure, the Samsung RIL will be a problem, but considering the HUGE interest in this phone, and the sheer numbers of users and devs who will have this phone, especially the Verizon version, I wouldn't worry too much.

We'll likely just have to be patient, which judging from this forum section, may be a lot more difficult than the RIL translation itself.
 
  • Like
Reactions: Mtn_Scott
The thing about AOSP seems to be that devs are always working a rev ahead of what the phone has working source for. So, when the SGS3 for verizon is released samsung is obligated to also release the source code for it at the same time. This makes it possible to create a good AOSP install for ICS, but i bet at that point that devs will be too trigger happy to hack Jelly Bean into it to bother doing much with the ICS version. This is what happened on most other phones, and it's more a culprit of the dev community only valuing "bleeding edge" and verizon always being a rev back on releases.