__________________ "Be the change that you wish to see in the world" -Mohandas Gandhi Site Rules & Guidelines | Read them, follow them, and be the example for fellow AF members.
I got clarification on source being dropped and for us toroplus users, we still don't have our binaries, only verizon (toro) does. Which means we'll still need to hack our way into receiving MMS, etc.
I got clarification on source being dropped and for us toroplus users, we still don't have our binaries, only verizon (toro) does. Which means we'll still need to hack our way into receiving MMS, etc.
So how long does that typically take? And what about kernels?
So how long does that typically take? And what about kernels?
Not sure but I'm sure we'll see updated JB ROM's as soon as late tonight or tomorrow morning. As long as source is available (even if not for our specific devices), we'll be fine. Look at what ACS did with a JB preview!!! This ROM (with the exception of MMS, which we have a fix for) is FLAWLESS!
As for kernels, we already have JB kernels that are the truth as is right now! With source available, they will just keep getting better.
The Following 2 Users Say Thank You to frenchy714 For This Useful Post:
I don't know.....I keep reading different things. Personally I think we will (in time), but at the end of the day, none of that matters. Same thing happened to the NS4G, it's not officially supported, and it didn't change anything; just like it won't change anything on the Gnex.
So does that mean official jelly bean support would come later?
I'm assuming so.....the Gnex *is* a Google phone, it would only make sense to. In the meantime we'll have near perfect ports popping up and awesome ROM's to play with.
Sure. I guess I still don't get what difference it makes for Sprint. What are they trying to protect? If the ports work and all the software updates still roll out, then what difference does it make? Does the phone lose any functionality by not being part of the AOSP?
LTE would be my main concern. I'm fortunate enough to live in one of the launch LTE cities, so as long as that work and all other aspects of the phone work just like you would expect with a Nexus phone, then I guess I can live with that.
Brimming with questions now....upgrading soon and I don't want to jump on this phone only to find out that there are drawbacks with it not being part of AOSP.
now maybe texting will work ....the fixes arent proving reliable...but im more dependent than most maybe.but great for us and not so great for apple ...but apples just stalling is all so it worked against apple....bullies dont aways win.lol..great google save samsung and ur self..may the force b with u.lol
.
Last edited by itiscosmo; July 10th, 2012 at 12:49 PM.
Device(s): Galaxy S3 (Verizon)
Evo 4G - retired/rooted
Carrier: Verizon
Thanks: 3,031
Thanked 1,721 Times in 1,162 Posts
Quote:
Originally Posted by MizzouBrent
Sure. I guess I still don't get what difference it makes for Sprint. What are they trying to protect? If the ports work and all the software updates still roll out, then what difference does it make? Does the phone lose any functionality by not being part of the AOSP?
LTE would be my main concern. I'm fortunate enough to live in one of the launch LTE cities, so as long as that work and all other aspects of the phone work just like you would expect with a Nexus phone, then I guess I can live with that.
Brimming with questions now....upgrading soon and I don't want to jump on this phone only to find out that there are drawbacks with it not being part of AOSP.
I think that being AOSP would be less work for sprint..? I mean, they would only have to release the binaries for the device right? Then google or devs take care of everything else. I think - correct me if I'm wrong. I don't think it loses 'functionality', but definitely timely updates - which IMO is a pretty big feature of the nexus line.
I feel I should follow this up by just saying that I too don't have the phone, and these are just my things that I'm thinking at 1 am.