As stated in the subject is Google supporting the GSM version before the LTE and is cyanogenmod focusing on the LTE more than the GSM?
Sent from my Galaxy Nexus using XDA App
GSM will probably get updates first, but it probably won't be by a discernible amount. They're working on both concurrently.
CM is focusing on both models.
So far, Toro has received them first.
4.0.2 was out for Toro before Maguro, but Toro wasn't released yet for sale.
4.0.4 is out for Toro, but not officially. Maguro hasn't seen a "leak" (4.0.4 is on an ota server for Toro, just not pushed).
Personally, I'd say its a crapshoot as to which is quicker (so far).
Most of the devs doing both release updates at the same time for both (its easy to do both).
The source will always be released for both at the same time, OTA's have been coming out on the LTE before though...it just depends.
I thought I read somewhere that Goog had dropped Toro as a dev phone - which would imply the Maguro is now top dog?
I'd hope so, I think maguro should be the first to get the updates considering it was the first one out
Sent from my Galaxy Nexus using XDA App
danger-rat said:
I thought I read somewhere that Goog had dropped Toro as a dev phone - which would imply the Maguro is now top dog?
Click to expand...
Click to collapse
Misconception, it was removed from their dev list along with all the CDMA phones due to CDMA needing proprietary files to join the network. Or at least that is how I understood the articles I read on it.
Sent from my Galaxy Nexus using Tapatalk
I just wish the updates came faster
_Dennis_ said:
Misconception, it was removed from their dev list along with all the CDMA phones due to CDMA needing proprietary files to join the network. Or at least that is how I understood the articles I read on it.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
That's about right. Basically the CDMA network stack required for full functionality on Sprint and Verizon isn't open source, so Google decided it wasn't a good idea to put up code that would effectively create incomplete builds for the NS4G, Xoom LTE, and VZW Galaxy Nexus.
Sent from my Galaxy Nexus using XDA App
So, logically, what would the alternative complete build be?
Considering any source released for one will be cooked into roms for both likely the same day it doesn't matter one bit.
danger-rat said:
So, logically, what would the alternative complete build be?
Click to expand...
Click to collapse
What comes out in the OTA... because that'll contain all the proper radios and network code.
Who gets the update first?
Of course people from the XDA forum, who else?
Take a look at current official version of Galaxy Nexus, 4.0.2.
What version are available? 4.0.3... If leaked 4.0.4 should not be counted...
Google is recently becoming sux at updates.
I would imagine upcoming ICS new phones will have newer version than the official Galaxy Nexus.
Sad, but that's the truth....
Sent from my Galaxy Nexus using xda premium
At the moment, neither
I just hope Google doesn't let ICS turn into another Honeycomb fiasco.
martonikaj said:
That's about right. Basically the CDMA network stack required for full functionality on Sprint and Verizon isn't open source, so Google decided it wasn't a good idea to put up code that would effectively create incomplete builds for the NS4G, Xoom LTE, and VZW Galaxy Nexus.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Almost.
The stack is open source, the blobs needed for it are not, and cannot be redistributed any longer. AOSP will not remove CDMA or LTE code from telephony.
martonikaj said:
What comes out in the OTA... because that'll contain all the proper radios and network code.
Click to expand...
Click to collapse
AOSP contains all required network code and will continue to do so. Us CDMA devs just have to be...creative in how we get our proprietary blobs.
adrynalyne said:
Almost.
The stack is open source, the blobs needed for it are not, and cannot be redistributed any longer. AOSP will not remove CDMA or LTE code from telephony.
Click to expand...
Click to collapse
adrynalyne said:
AOSP contains all required network code and will continue to do so. Us CDMA devs just have to be...creative in how we get our proprietary blobs.
Click to expand...
Click to collapse
Thanks for the slight clarification. I was just trying to generalize to make it easy to digest.
I'd like to say maguro gets it first as toro had the leaked 4.0.4 but then perhaps that's more reason they would get it first. I wouldn't of thought there will be much in it, less than a few days I hope.
Sent from my Galaxy Nexus using Tapatalk
Related
Hi guys !
I just wanted to say that SFR France announced Android 4.0.5 for the Galaxy Nexus, and it should arrive on March according to them. Given the fact that they modify the ROM, the official build may arrive sooner !
Picture/Link/Proof or didn't happen.
http://android.sfr.fr/maj-optimisez-votre-mobile-android-mettez-le-a-jour-previsions-7
Course, I'd rather see 4.0.4 for GSM at the moment
Such a table can everyone create. I dont trust such news without evidence.
4.0.4 and 4.0.3 aren't official released yet and you're debating about 4.0.5.
I heard it makes the battery last for a week on 1 charge.
This website is official.(sfr)
Sfr is a French mobile provider and they always provide "such a table" about future firmware update.
http://www.frandroid.com/actualites-generales/92001_sfr-annonce-android-4-0-5-pour-le-galaxy-nexus-et-le-nexus-pour-le-mois-de-mars/?utm_source=feedburner&utm_medium=twitter&utm_campaign=Feed%3A+Frandroid+%28FrAndroid%29
Sent from my Galaxy Nexus using XDA App
Oh seems nice. I'm SFR user and will reposte here if I get the ota in Mars. I wonder how they'll modify the room. If it turn out to be worse than custom roms I'll not be surprised.
With all the ics version numbers flying around it's hard to keep track. This 4.0.5 thingy would probably be something similar to 4.0.4 for Verizon LTE update but exclusive for SFR users.
Sent from my Galaxy Nexus using XDA App
Leandros_Ger said:
Such a table can everyone create. I dont trust such news without evidence.
4.0.4 and 4.0.3 aren't official released yet and you're debating about 4.0.5.
Click to expand...
Click to collapse
And yes the website is official.
4.0.3 isn't out for perfection reasons I think [sorry my bad again, 4.0.3 isn't meant for GNex apparently] and 4.0.4 is exclusive for [scratch that] LTE users, so SFR users getting a 4.0.5 update is not really surprising.
Sent from my Galaxy Nexus using XDA App
tauruslei said:
And yes the website is official.
4.0.3 isn't out for perfection reasons I think
Click to expand...
Click to collapse
iirc i wasnt actually intended for the galaxy nexus.
tauruslei said:
And yes the website is official.
4.0.3 isn't out for perfection reasons I think and 4.0.4 is exclusive for Verizon LTE users, so SFR users getting a 4.0.5 update is not really surprising.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Why do you think 4.0.4 is exclusive for Verizon? I really really doubt it.
Leandros_Ger said:
Such a table can everyone create. I dont trust such news without evidence.
4.0.4 and 4.0.3 aren't official released yet and you're debating about 4.0.5.
Click to expand...
Click to collapse
You wont get any evidence before it is actually released. SFR can say whatever they want, and any Android developper can, too.
I'm just sorry I did not post a link first.
No x.x.x version is exclusively for a specific carrier.
Sent from my Galaxy Nexus using xda premium
ErGo_404 said:
Hi guys !
I just wanted to say that SFR France announced Android 4.0.5 for the Galaxy Nexus, and it should arrive on March according to them. Given the fact that they modify the ROM, the official build may arrive sooner !
Click to expand...
Click to collapse
4.0.4 I have has a build date of Feb 1st.
I doubt 4.0.5 will be seen this month. We shall see of course.
mike1986. said:
Why do you think 4.0.4 is exclusive for Verizon? I really really doubt it.
Click to expand...
Click to collapse
OK my bad. Not exclusive for Verizon but probably for LTE version.
Fact is I don't know any of this for sure
So, Google is going to fragment the Galaxy Nexus line?
Heh.
mike1986. said:
Why do you think 4.0.4 is exclusive for Verizon? I really really doubt it.
Click to expand...
Click to collapse
Depending on what changed it may be an incremental update to address LTE /CDMA issues. If this is the case it would not be pushed to GSM handsets. This was done with the Nexus S / Nexus S 4G. It has nothing to do with exclusivity but does lead to devices running different minor versions.
When appropriate an OTA will be pushed for GSM devices as well, it may be 4.0.4 or a later minor release such as 4.0.5.
Sent from my Galaxy Nexus using xda premium
adrynalyne said:
So, Google is going to fragment the Galaxy Nexus line?
Heh.
Click to expand...
Click to collapse
Minor version differences are not "fragmentation".
Sent from my Galaxy Nexus using xda premium
adrynalyne said:
4.0.4 I have has a build date of Feb 1st.
I doubt 4.0.5 will be seen this month. We shall see of course.
Click to expand...
Click to collapse
Is the 4.0.4 build for Verizon? I just did check for update on an unlocked unrooted phone, it said it was up to date on 4.0.2.
TIA!
krohnjw said:
Minor version differences are not "fragmentation".
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It certainly is.
Same as 2.3.x versions in the past. 4.0.4 is not officially out. One user got it, we helped pull it. Thats not enough to draw such conclusions from. LTE issues will be resolved in ril and radios. That can be shipped with any build.
Don't forget LTE telephony code is now native to Android as of ICS. There is no reason for fragmentation.
NookMonkey said:
Is the 4.0.4 build for Verizon? I just did check for update on an unlocked unrooted phone, it said it was up to date on 4.0.2.
TIA!
Click to expand...
Click to collapse
Not officially out. Not...really.
Is 4.0.3 or 4.0.4 stock OTA ROM out for GSM Galaxy Nexus yet? Just making sure I haven't missed anything.
Why is 4.0.4 out for Verizon but we're still on 2?
Sent from my Galaxy Nexus using Tapatalk
We have a 4.0.3 and 4.0.4 rom. Check the development section. Another 4.0.4 rom is set to be released as well called Foxhound. It is currently being worked on.
Sent from my Galaxy Nexus using XDA Premium App
Just root the phone already. -_-
Sent from my Galaxy Nexus using XDA App
4.0.2 is the latest version of OTA for both CDMA and GSM.
We only have 4.0.3 ROMs because the source trees have been updated but no OTA yet. We have 4.0.4 for CDMA phones because there was one leak and its been put into ROMs.
If you're not going to root, you just gotta wait.
Sorry I should've been clearer.
I am rooted, but was enquiring about the OTA stock ROM versions. Thanks for the answer above!
Sent from my Galaxy Nexus using Tapatalk
both versions of the phone are updated to 4.0.2 via OTA, 4.0.3 was only released as source and 4.0.4 was leaked for the LTE
Sent from my Galaxy Nexus using XDA App
CJSnet said:
Sorry I should've been clearer.
I am rooted, but am enquiring about the OTA stock ROM versions. Are we still on 4.0.2 and if so... Huh?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Read my post. 4.0.2 is the latest OTA.
martonikaj said:
Read my post. 4.0.2 is the latest OTA.
Click to expand...
Click to collapse
Yes, we posted simultaneously ;-)
Sent from my Galaxy Nexus using Tapatalk
CJSnet said:
Sorry I should've been clearer.
I am rooted, but am enquiring about the OTA stock ROM versions. Are we still on 4.0.2 and if so... Huh?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
GSM is up to 4.0.2 ota we have 4.0.3 roms and one 4.0.4 rom so far for the i9250 GSM model.
Hope that helps.
Sent from my Galaxy Nexus using XDA Premium App
and yet devices like the toshiba a200 are getting updates before our phones. Ridiculous.
I don't see much difference between 4.0.2 stock and 4.0.3 custom r
biggiestuff said:
and yet devices like the toshiba a200 are getting updates before our phones. Ridiculous.
Click to expand...
Click to collapse
le sigh...
biggiestuff said:
and yet devices like the toshiba a200 are getting updates before our phones. Ridiculous.
Click to expand...
Click to collapse
Pardon me?
Devices may get the latest update before we do, but this does not guarantee the build they receive will be stable and bug free. Also keep in mind predicted release dates are different than actual release dates.
Be patient, enjoy your hardware, and stop worrying about a single digit.
I'm fully aware there are a few complications with the current 4.0.2 builds, but its nothing detrimental to daily usage.
Also I know this is a Google based phone, but users have only insinuated that Google will update the nexus first, Google has not said the nexus will be first.
Sent from my Galaxy Nexus using xda premium
Well if the Acer A200 is getting 4.0.3 already, I guess it means ours can't be too much longer.
You serious? The performance is much improved, especially the stock browser and app switcher. I tested out a custom ROM to checkout the differences, but ended up immediately going back to stock because I can't bring my self to trust what a custom ROM is doing with my phone and data (no offense to any devs here). I tried to build my own from AOSP but gave up.
I'm impatiently waiting for the official OTA now.
heo_con184 said:
I don't see much difference between 4.0.2 stock and 4.0.3 custom r
Click to expand...
Click to collapse
This is lame, been waiting for 4.0.3 for two months basically.
I realize we'll get it before most devices but still, I didn't think it would take this long for actual OTA updates to come out after the source is released.
heo_con184 said:
I don't see much difference between 4.0.2 stock and 4.0.3 custom r
Click to expand...
Click to collapse
You clearly don't use IPSec VPNs over HSDPA then
martonikaj said:
4.0.2 is the latest version of OTA for both CDMA and GSM.
We only have 4.0.3 ROMs because the source trees have been updated but no OTA yet. We have 4.0.4 for CDMA phones because there was one leak and its been put into ROMs.
If you're not going to root, you just gotta wait.
Click to expand...
Click to collapse
Smokeey said:
both versions of the phone are updated to 4.0.2 via OTA, 4.0.3 was only released as source and 4.0.4 was leaked for the LTE
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Actually the 4.0.4 for the Verizon Galaxy Nexus is officially available... I got the OTA update and built a stock ROM over that... and here's the download link from Google... http://android.clients.google.com/p....signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip
I have 4.0.3 on my transformer prime, maybe it's just a tablet upgrade?? and the phones will get a 4.0.4 soon
I would be willing to run logcats, test installs, and check features for alpha testing, but I am curious to learn more about whether or not HTC has released the source code on the PrimoC yet. If anyone knows...I wud appreciate the help.
Molikai1988 said:
I would be willing to run logcats, test installs, and check features for alpha testing, but I am curious to learn more about whether or not HTC has released the source code on the PrimoC yet. If anyone knows...I wud appreciate the help.
Click to expand...
Click to collapse
No, they haven't.
Sent from my HTC One V using Tapatalk 2
I am beginning to wonder if this is Virgin Mobile not letting them. If they won't release the source to the cdma but they will for the GSM then perhaps a reverse compile is possible. If the code is similar enough then using the source from the GSM as a base could yield some source.
Molikai1988 said:
I am beginning to wonder if this is Virgin Mobile not letting them. If they won't release the source to the cdma but they will for the GSM then perhaps a reverse compile is possible. If the code is similar enough then using the source from the GSM as a base could yield some source.
Click to expand...
Click to collapse
CDMA CM9 needs custom kernel for audio. That's all I known
Sent from my HTC Desire using xda premium
Lloir said:
CDMA CM9 needs custom kernel for audio. That's all I known
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
So the hardware should be close, but I see that this is true about the audio...will have to keep one eye on HTC for the source...till then I guess its NoN-sEnSe primo-c 1.1.
I don't think it would be Virgin Mobile calling the shots imo. They would lose potential sales whereas HTC will find a different carrier.
Yeah I just checked with a guy I know that works support for htc. He said its scheduled soon. So at least its soon lol. Just wish he cud say when.
Sent from my HTC One V using xda app-developers app
Molikai1988 said:
Yeah I just checked with a guy I know that works support for htc. He said its scheduled soon. So at least its soon lol. Just wish he cud say when.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
really? cause im honestly saying close to the end of august or beginning of september. This is their track record....
I also talked to them about the kernel source for CDMA/Virgin Mobile USA HTC ONE V, they do have plans to release the source however it takes longer for CDMA vs GSM, something to do with the more proprietary nature of CDMA, we've seen this cause delays with AOSP build on CDMA Nexus Devices, so it doesn't surprise me that it's taking longer to release. However in the mean time the hardware differences between GSM and CDMA variants should be minuscule (cellular data being the obvious one) so could we continue making the build without data/sound and just add those when the drivers are available so time isn't wasted on waiting for sources to be released? I would be willing to test.
MtDewFella said:
I also talked to them about the kernel source for CDMA/Virgin Mobile USA HTC ONE V, they do have plans to release the source however it takes longer for CDMA vs GSM, something to do with the more proprietary nature of CDMA, we've seen this cause delays with AOSP build on CDMA Nexus Devices, so it doesn't surprise me that it's taking longer to release. However in the mean time the hardware differences between GSM and CDMA variants should be minuscule (cellular data being the obvious one) so could we continue making the build without data/sound and just add those when the drivers are available so time isn't wasted on waiting for sources to be released? I would be willing to test.
Click to expand...
Click to collapse
I already have a thread up for CM9. I am releasing a new one today that has sound working and is on par with the GSM version status.
jmztaylor said:
I already have a thread up for CM9. I am releasing a new one today that has sound working and is on par with the GSM version status.
Click to expand...
Click to collapse
Yup just found it, like I said over there, I'll risk my phone in testing (joking, I don't actually believe your build will destroy my phone, this isn't my first beta testing rodeo) for the benefit of the Greater android community.
I have read that the k at the end of a build number means its updated by Samsung. My build number is IMM76K. The question I have my system update button only says check now. My gf Samsung SIII has Samsung update check and firmware update check button, so is mine updated by Sprint, Samsung, or Google?
Sent from my Galaxy Nexus using Tapatalk 2
BlackKnight said:
I have read that the k at the end of a build number means its updated by Samsung. My build number is IMM76K. The question I have my system update button only says check now. My gf Samsung SIII has Samsung update check and firmware update check button, so is mine updated by Sprint, Samsung, or Google?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The K doesn't have anything to do with Samsung. However, your official update will come through Sprint, as they do not release the binaries to Google so they can update "their" device like the GSM version.
Sent from my AOSP Android 4.1.1 Galaxy Nexus
Thanks for clarifying. One thing I read is the binaries for the Nexus S 4g were released will this eventually help / lead to the Nexus?
Sent from my Galaxy Nexus using Tapatalk 2
BlackKnight said:
Thanks for clarifying. One thing I read is the binaries for the Galaxy S 4g were released will this eventually help / lead to the Nexus?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
you have no idea what you are reading.
different phones.. how can it help?
We "have" fully functional AOSP 4.1.1 through custom ROMs. We don't need anything to help. If you want a great pure stock experience and have the Sprint version (Toroplus), then grab the newly released version of Purely AOSP. Completely stock based build of AOSP 4.1.1 JRO03H. Runs flawless, no broken features, no bugs.
Sent from my AOSP Android 4.1.1 Galaxy Nexus
Zepius said:
you have no idea what you are reading.
different phones.. how can it help?
Click to expand...
Click to collapse
I understand what you're saying. Binaries are only useful to the device they were released for. That aside, if we were talking about Nexus S/GB, it would be a different story, since binaries source was released. Several samsung devices (like i9000) had CM support because of this.
Sent from my tf201
So I know Replicant is not available for this phone since it is CDMA. Are there any other OS alternatives for the toro other than Android?
I'm wondering if there is an obscure OS that I haven't heard about yet. Full functionality is not required, just looking for something to play, with a least marginal support.
Ubuntu?
Sent from my VS980 4G using Tapatalk
comk4ver said:
Ubuntu?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I didn't know ubuntu supported the toro. I'll check it out, thanks!
SynbiosVyse said:
I didn't know ubuntu supported the toro. I'll check it out, thanks!
Click to expand...
Click to collapse
I don't think they officially support the verizon galaxy nexus.. There are pages that show you how to modify the other variants to get it to work though.