Google stated they "No longer support CDMA Devices"
This article here, shows that the Verizon Galaxy Nexus is no longer supported for android. This may mean that all CDMA devices will never get any updates from this point on.
Not sure if this pertains to our phones receiving OTA ICS though.
I have GSM... but that's really effed up on Google's Part ...
- Google
tylerwatt12 said:
Google stated they "No longer support CDMA Devices"
This article here, shows that the Verizon Galaxy Nexus is no longer supported for android. This may mean that all CDMA devices will never get any updates from this point on.
Not sure if this pertains to our phones receiving OTA ICS though.
Click to expand...
Click to collapse
WTF?!?!?!
sent from my iPad Wheel using Rotatalk
This has to be a misunderstanding.
I have a GSM version. But hopefully google replies to this soon, it seems kind of strange!
Wth!
sent from my ice cream nexus via tapatalk
WTF!!!!! This is insane...
We're fine our good friend Burnsra posted this comment on that link above.
Burnsra
Collapse
Source changes http://goo.gl/65Uwj http://goo.gl/jBKm2
Yes source changes they removed crespo4g and toro from the vendorSetup.sh LOL....
Hopefully we'll get an answer soon.
WTF!
Ok so this means no source code published for NS4g anymore... so no more ROMs?? WTF!!!!!!
rasengan82 said:
Ok so this means no source code published for NS4g anymore... so no more ROMs?? WTF!!!!!!
Click to expand...
Click to collapse
They still have to publish the source. It just means it isn't a "developer phone" anymore, so they will not support it in AOSP has a default build. They aren't going to abandon OTA updates for the device. It seems to be more of a way to streamline AOSP so there aren't so many configurations. They did the same for the CDMA Galaxy Nexus.
https://groups.google.com/forum/?fromgroups#!topic/android-contrib/phz3S5ZdveU
I sense a lot of panties being tied in knots over something that barely qualifies as important.
Could 4.0.4 leak with sprint TV&movies have something to do with ns4g drop?
So, if I'm understanding correctly... nothing has changed except that Google is removing CDMA devices from their *instructions* for building from AOSP?
If so I wish they'd just say it in stupid-English so I can understand
jesusice said:
So, if I'm understanding correctly... nothing has changed except that Google is removing CDMA devices from their *instructions* for building from AOSP?
If so I wish they'd just say it in stupid-English so I can understand
Click to expand...
Click to collapse
They don't want to figure out how to make .APKs work with cdma phones.. Lazy ass work ethic.. They must not have enough money to hire cdma devs..
Sent from my Nexus S 4G using xda premium
lazydazed said:
They don't want to figure out how to make .APKs work with cdma phones.. Lazy ass work ethic.. They must not have enough money to hire cdma devs..
Click to expand...
Click to collapse
They know exactly how to make the apk's work. But they aren't providing the private keys to developers. That is the issue.
Does this make it harder for future ports/unofficial ROMs? IE: if this happened before ICS, would we still be waiting (ignoring the recent leak) for a official OTA to get a WiMax enabled ICS?
Sent from my Nexus S 4G using Tapatalk
Related
http://www.engadget.com/2011/04/16/...pdate-now-rolling-out-across-europe/#comments
kinda sad that a phone thats been out for almost a year is getting gingerbread before the atrix. i think its ATT's fault. they seem to delay OS updates, at least they did for the captivate. both rogers and bell got froyo months before att. maybe ATT wants to make sure all the features it wants disabled are in working like wifi hotspot?
True. Im already regretting buying my Atrix, too late to return it though. But also Motorola was asking for beta testers to sign up to test 2.3.
neotekz said:
http://www.engadget.com/2011/04/16/...pdate-now-rolling-out-across-europe/#comments
kinda sad that a phone thats been out for almost a year is getting gingerbread before the atrix. i think its ATT's fault. they seem to delay OS updates, at least they did for the captivate. both rogers and bell got froyo months before att. maybe ATT wants to make sure all the features it wants disabled are in working like wifi hotspot?
Click to expand...
Click to collapse
Looks like this is for unbranded galaxy s phones though. In the US it takes longer cause the carriers are modding the OS to add all their useless bloatware crappola an it's usually the carrier that pushes the updates not the manufacturer. But hopefully with the update to enable hsupa we get a couple of extra goodies.
Sent from my MB860 using XDA Premium App
Magic_Bunny said:
True. Im already regretting buying my Atrix, too late to return it though. But also Motorola was asking for beta testers to sign up to test 2.3.
Click to expand...
Click to collapse
motorola is getting beta testers for gingerbread? did they put up a sign up like for the update or just announce it?
Motor is asking for beta testers? If so...then GB will be released
Sent from my MB860 using XDA App
Motorola isnt beta testing 2.3
blaque72 said:
Motorola isnt beta testing 2.3
Click to expand...
Click to collapse
+1.
I'll believe it when I see it myself!
Sent from my MB860 Atrix using XDA App.
it makes sense that the phone that's been out for a year gets it first....
since google released the 2.3 source code, the company has been doing nothing but preparing an update most likely. motorola however, needed to iron out kinks in their initial 2.2 release before they can consider developing a 2.3 OS, and then allowing carriers to modify it to your liking.
obviously you didn't think about what has to be done to come up with a polished 2.3 update before it can be released as an official OTA update. you really can't fault motorola for this not being out yet. it takes a lot of time, testing, and effort to release a finished product.
Raybond, I agree with everything you said, but its hard to cut Motorola any slack for this when the phone should have come with 2.3 in the first place. On top of that they lock the bootloader so we cant get 2.3 working on our own either....
Silent8Strike said:
Raybond, I agree with everything you said, but its hard to cut Motorola any slack for this when the phone should have come with 2.3 in the first place. On top of that they lock the bootloader so we cant get 2.3 working on our own either....
Click to expand...
Click to collapse
well, the problem is that they probably started dev for the atrix's OS before 2.3 was released, so it would have been even more work, and probably would have caused delays in their release of the phone if they had shipped it with 2.3
I know locked bootloader is a massive drag for 3rd party dev, but you really can't fault moto for any decisions they've made with this phone other than that.
drock212 said:
Looks like this is for unbranded galaxy s phones though. In the US it takes longer cause the carriers are modding the OS to add all their useless bloatware crappola an it's usually the carrier that pushes the updates not the manufacturer. But hopefully with the update to enable hsupa we get a couple of extra goodies.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I guess this is the price we pay for having a subsidized drvice. Unfortunately... although we pay double for it in years of service.
Sent from my MB860 using XDA App
slimslim said:
I guess this is the price we pay for having a subsidized drvice. Unfortunately... although we pay double for it in years of service.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
not really, you are going to be paying a carrier either way just without a contract. the cost of the subsidy doesnt get added to your bill. either this or buy a phone for full price like in europe.
i read that google is going to be releasing ice cream sandwich sometime this summer. maybe motorola is going to skip gingerbread? i wouldnt mind waiting until the end of the year if it means we get 2.4.
neotekz said:
not really, you are going to be paying a carrier either way just without a contract. the cost of the subsidy doesnt get added to your bill. either this or buy a phone for full price like in europe.
i read that google is going to be releasing ice cream sandwich sometime this summer. maybe motorola is going to skip gingerbread? i wouldnt mind waiting until the end of the year if it means we get 2.4.
Click to expand...
Click to collapse
You would have to skip over "Gingerbread" AND "Honeycomb" to get to ICS.
That's not gonna happen...
bigb252 said:
+1.
I'll believe it when I see it myself!
Sent from my MB860 Atrix using XDA App.
Click to expand...
Click to collapse
Yes moto does.
I read it on moto official forum.
And you need to fill a form or something before a date...
I would if my phone wasn't unlocked..
---------------
EDIT:
My fault!!!! Sorry guys!!!
I didn't read the whole post from moto forum. At the end of that post there is an edit, that says it was about the 1.5.7 update we already got! My mistake, my fault, sorry
Sent from my MB860 using XDA App
ccrows said:
You would have to skip over "Gingerbread" AND "Honeycomb" to get to ICS.
That's not gonna happen...
Click to expand...
Click to collapse
actually you're not skipping honeycomb....
honeycomb is a totally different series in Android OS, tablet-specific series to be precise (3.0)
So, gingerbread is 2.3, and ICS is 2.4. Also, rumour has it that ICS will have full dual-core support, so it would make logical sense for Moto to not waste any time with 2.3 and go straight for dev in 2.4
ccrows said:
You would have to skip over "Gingerbread" AND "Honeycomb" to get to ICS.
That's not gonna happen...
Click to expand...
Click to collapse
ice creme sandwich is a blend features of both gingerbread and honeycomb made specifically for phones. you will not be seeing honeycomb on an android phone backed by google. that one reason google is not releasing honeycomb source yet, they dont want to have honeycomb phones out there.
raybond25 said:
So, gingerbread is 2.3, and ICS is 2.4. Also, rumour has it that ICS will have full dual-core support, so it would make logical sense for Moto to not waste any time with 2.3 and go straight for dev in 2.4
Click to expand...
Click to collapse
i thought gingerbread is suppost to be optimized for dual cores too.
Paschalis said:
Yes moto does.
I read it on moto official forum.
And you need to fill a form or something before a date...
I would if my phone wasn't unlocked..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
link please?
neotekz said:
ice creme sandwich is a blend features of both gingerbread and honeycomb made specifically for phones. you will not be seeing honeycomb on an android phone backed by google. that one reason google is not releasing honeycomb source yet, they dont want to have honeycomb phones out there.
i thought gingerbread is suppost to be optimized for dual cores too.
Click to expand...
Click to collapse
i believe that it has some modicum of support for dual core, but is not completely optimized for it as 2.4 will be.
that's just my understanding, if someone could provide a link to prove me wrong then i'd freely accept it.
Gingerbread as currently released for SGS has some glitches but guess what Samsung just released the source code! So we should be seeing fixes and tricked out kernels/ROMS/system apps very soon.
http://forum.xda-developers.com/showthread.php?p=12992329&posted=1#post12992329
bigb252 said:
+1.
I'll believe it when I see it myself!
Sent from my MB860 Atrix using XDA App.
Click to expand...
Click to collapse
I saw the signup sheet too. It never hurts to waste a little time each day looking through these forums. I swear I saw a link for it. I looked at it and saw some sign up thingy on Motorola's website.
Just thought I'd share this article, with the hope that someone else had information regarding the rumor.
Sprint Working Nexus S 4G Update To OS 2.4?
What do ya'll think?
I think....
Sent from my Nexus S 4G using XDA App
I thought google pushed our updates. Or is it a collaborative effort?
Uncle Jimmy says hello
snandlal said:
I thought google pushed our updates. Or is it a collaborative effort?
Uncle Jimmy says hello
Click to expand...
Click to collapse
They do. The blog article is probably wrong. Though Sprint may work with Samsung on radio firmware.
matt2053 said:
They do. The blog article is probably wrong. Though Sprint may work with Samsung on radio firmware.
Click to expand...
Click to collapse
That was my thought about the rumor. It didn't make sense considering an update to 2.3.4 would come from Google. But, it seems that the signal issues are directly related to the 4G radio or its accompanying firmware.
My guess is that Google would need to work with Sprint and possibly Samsung to address the issue.
The whole reason I purchased the Nexus S was the updates for the OS would come from GOOGLE not Sprint. They did mention in the article that radio sucked and was testing it. I am not sure if 2.4 would drop our way or not. I am coming from an EPIC. The updates were far and few. They were real buggy also. Great phone but the last 2 months developers for the EPIC dropped like flies.
The article clearly is misinformed. The update will only effect the radio on Sprint's side and Google would send their part as 2.4. Now, unless their tipster is completely off, this would be the only "collaboration" Sprint and Google would have. And Samsung... I'm not sure what they are supposed to do. They made the device. What else can they do?
Sent from my Nexus S 4G using XDA App
obsanity said:
The article clearly is misinformed. The update will only effect the radio on Sprint's side and Google would send their part as 2.4. Now, unless their tipster is completely off, this would be the only "collaboration" Sprint and Google would have. And Samsung... I'm not sure what they are supposed to do. They made the device. What else can they do?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
True dat
Uncle Jimmy says hello
nowens0520 said:
Just thought I'd share this article, with the hope that someone else had information regarding the rumor.
Sprint Working Nexus S 4G Update To OS 2.4?
What do ya'll think?
Click to expand...
Click to collapse
I doubt a bug fix for a single device would merit a full .1 version increase. But who knows, maybe they don't want the phone OS to skip a letter before Ice Cream Sandwich. 2.3= Gingerbread. 2.4= Haha, Jk.
obsanity said:
The article clearly is misinformed. The update will only effect the radio on Sprint's side and Google would send their part as 2.4. Now, unless their tipster is completely off, this would be the only "collaboration" Sprint and Google would have. And Samsung... I'm not sure what they are supposed to do. They made the device. What else can they do?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Samsung supplies the CDMA radio drivers.
Sent from my Nexus S using XDA App
bencozzy said:
Sounds like they are working on a driver fix to push out with 2.4 os only thing is that 2.4 won't be out until late august at best. They'd going to be googles biggest os push to so many devices. The nexus and some dual cores will see out first then the test of the dual cores maybe some high end single cores will see it up to the manufacture if they put it out our not.
Click to expand...
Click to collapse
what???...
mikeyinid said:
what???...
Click to expand...
Click to collapse
Yeah..... what?
...the source code for Android version 4.0 (Ice Cream Sandwich) is now available
Click to expand...
Click to collapse
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device.
Click to expand...
Click to collapse
Awesome! On your marks, get set, port!
http://groups.google.com/group/android-building/msg/c0e01b4619a1455a?pli=1
I smell CM9.
Sent from my R800x
Noob question:
What exactly does this mean?
Cl8rs said:
Noob question:
What exactly does this mean?
Click to expand...
Click to collapse
nothing to us noobs
means they could build custom roms and such, but us noobs dont need to worry about those we can just sit and wait for an official version (if) from sony.
DrEzkimo said:
nothing to us noobs
means they could build custom roms and such, but us noobs dont need to worry about those we can just sit and wait for an official version (if) from sony.
Click to expand...
Click to collapse
Yeah, not too much interested in ROMs at the moment. I've had them in the past, but this phone doesn't need it Besides I have a locked Bootloader...
Cl8rs said:
Noob question:
What exactly does this mean?
Click to expand...
Click to collapse
It means that people can start porting / developing ICS related content. Your likely to see Cyanogenmod supporting 4.0.1 before its released from SE (or rather, Sony now.)
EDIT: If your on an R800x there is a Very good chance you will never live to see the day Verizon supports ICS on this device. Especially with the low sales.
Sent from my R800x
Leraeniesh said:
It means that people can start porting / developing ICS related content. Your likely to see Cyanogenmod supporting 4.0.1 before its released from SE (or rather, Sony now.)
EDIT: If your on an R800x there is a Very good chance you will never live to see the day Verizon supports ICS on this device. Especially with the low sales.
Sent from my R800x
Click to expand...
Click to collapse
That's why we has XDA!..
Sent from my Xoom using Tapatalk
The r800x is and most likely will always be the odd ball out. Its just easier for devs to get it working for gsm phones cause they all have one instead of going through the pain in the ass for a cdma phones
Sent from my R800i using XDA App
http://blogs.sonyericsson.com/produ...ich-for-sony-ericsson-2011-xperia™-portfolio/
http://www.engadget.com/2012/03/15/confirmed-ics-coming-to-the-nexus-s-in-the-next-few-weeks/
OTA for all countries or 4.0.5???
Hopefully it's more stable than 4.0.3 was.
Sent from my Xoom using Tapatalk
climhz said:
http://www.engadget.com/2012/03/15/confirmed-ics-coming-to-the-nexus-s-in-the-next-few-weeks/
OTA for all countries or 4.0.5???
Click to expand...
Click to collapse
What do you mean what is it? It will be ICS finally rolling out after all these months to all the variants. And yes, it will be a bug fix release to the T-mobile version that partially rolled out too.
Can wait for a DEV out there to get it hands dirty with it!!!
Some reliable sources say this time its the real deal.
obsanity said:
Some reliable sources say this time its the real deal.
Click to expand...
Click to collapse
That's what they always say. Not impressed.
Engadget shoulda have more specific details, e.g., the version. I have been rocking ICS since the stock ICS OTA rolled out to T-Mobile, and now AOKP.
Sent from my Nexus S using xda premium
063_XOBX said:
That's what they always say. Not impressed.
Click to expand...
Click to collapse
Engadget wouldn't post that information unless it was from a source inside of Google. Unlike some of these crack pot bloggers, they actually have real sources.
bozzykid said:
Engadget wouldn't post that information unless it was from a source inside of Google. Unlike some of these crack pot bloggers, they actually have real sources.
Click to expand...
Click to collapse
They used to....
obsanity said:
They used to....
Click to expand...
Click to collapse
If it was from an external source, they would tell you their sources. Since they didn't, then you can be almost 100% positive it was from someone inside of Google.
obsanity said:
They used to....
Click to expand...
Click to collapse
Myriam Joire is the real deal man. She has great sources, and I've yet to ever hear her say anything that hasn't been reliable, credible, and ultimately proven true.
Sent from my Nexus S using Tapatalk
Even I can estimate like this lol.
Sent from my Nexus S 4G using XDA
uansari1 said:
Myriam Joire is the real deal man. She has great sources, and I've yet to ever hear her say anything that hasn't been reliable, credible, and ultimately proven true.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Myriam is a guy.
karnoff said:
Myriam is a guy.
Click to expand...
Click to collapse
Uhh, no, Myriam is a woman according to her Engadget bio page. Yes, she may look like a man (all joking aside), but she is not.
I wish, it would have better battery life
Sent from my Nexus S using xda premium
The reason there is such a delay this time around has to deal with the fact google has removed the support from cdma devices officially. This means in order to supply updates, we have to wait for sprint. Currently Sprint is bitter about the who deal. We are the ones who will suffer in the long run.
Same for why the gnex for sprint isn't out quite yet.
lithid-cm said:
The reason there is such a delay this time around has to deal with the fact google has removed the support from cdma devices officially. This means in order to supply updates, we have to wait for sprint. Currently Sprint is bitter about the who deal. We are the ones who will suffer in the long run.
Click to expand...
Click to collapse
The release was pulled from T-mobile and never existed for AT&T. So unless you are saying those are CDMA carriers as well, your theory makes no sense. All 3 device types currently are waiting for an ICS update. Google is surely working to make that happen. But Sprint isn't holding up the release (at least not yet) because it doesn't even exist. And Google removing CDMA from ASOP has no bearing on the speed at which they provide the update. The process is the same. The problem is the lack of understanding of why CDMA was pulled from ASOP and the sensationalist articles spewing incorrect information has probably confused you.
Tired of waiting..
I think Google takes too long to release an OTA!
bozzykid said:
The release was pulled from T-mobile and never existed for AT&T. So unless you are saying those are CDMA carriers as well, your theory makes no sense. All 3 device types currently are waiting for an ICS update. Google is surely working to make that happen. But Sprint isn't holding up the release (at least not yet) because it doesn't even exist. And Google removing CDMA from ASOP has no bearing on the speed at which they provide the update. The process is the same. The problem is the lack of understanding of why CDMA was pulled from ASOP and the sensationalist articles spewing incorrect information has probably confused you.
Click to expand...
Click to collapse
I guess you work with stuff on a daily basis? This is a google phone, if you don't think GSM variants are not affected by google move to drop cdma support your mistaken. There is alot more that goes on behind the scenes the push code > compile > update. Countless documents, this need to get removed, shuffled and put back into order once again. Instead of google being about to push updates with the help of carriers, google and the nexus s is now fragmented. To ensure a proper release cycle it will take longer then expected. Pulling a phone from official support isn't like dropping your kids off at school.
lithid-cm said:
I guess you work with stuff on a daily basis? This is a google phone, if you don't think GSM variants are not affected by google move to drop cdma support your mistaken. There is alot more that goes on behind the scenes the push code > compile > update. Countless documents, this need to get removed, shuffled and put back into order once again. Instead of google being about to push updates with the help of carriers, google and the nexus s is now fragmented. To ensure a proper release cycle it will take longer then expected. Pulling a phone from official support isn't like dropping your kids off at school.
Click to expand...
Click to collapse
Actually, Google didn't drop support for the CMDA variants except in ASOP. So there is no change in the way they rolled out updates. So you are saying they pulled the buggy release because they anticipated dropping CDMA months later? I guess the AT&T version didn't get the release in December because they were dropping CDMA support several months later? I feel like you are drawing conclusions that aren't even there.
Don't get me wrong I appreciate what we've got so far from a couple devs but each rom has some problems, and an official build port would be awesome! (No 4G but who cares).
From what i know its not too hard, i attempted but i still cant get 3G cause i suck. :silly:
A port of AdamG's build or something would be cool too, i'll take anything!
Hope i'm not coming off the wrong way here, Thanks!
word
*bump* I would love to see a stock JB port as well. :highfive:
I've said the same thing a port of the official ota would be real great with everything working except 4g I'll take that in a heart beat but its all good I ain't *****ing the devs already do a great job so its there time if they want to do the port its up to them!
Sent from my Nexus S 4G using xda premium
4g love would be nice. If I had more time on my hands, the current stagnation in development would be a perfect motivator to learn the porting process.
Sprint has proven to be unfriendly to nexus devices and the development community. Due to this experience, I will likely change carriers once my contract ends.
I'd imagine that the devs currently working on ROMs have looked at porting from the Nexus S...or at least I'd hope so. If I knew ANYTHING about working on ROMs, I'd give it a shot, but wouldn't know where to start. If it's not too difficult, and with MichaelCampos having 4g working on his ROM, I don't see why we wouldn't have a fully functional stock ROM available....
There isn't even a fully functional ROM without 4g.
MMS and GPS are a problem on both ROMs. You have to have gosms to view MMS messages.
I'm starting to think we will have to wait it out until the binaries are release to aosp before we get a fully functioning rom. That will probably be awhile because the aosp guy is on vacation... or so his twitter says.
http://twitter.com/jbqueru/status/226429502182531072
Oh well. The wait continues
Sent from my Nexus S 4G using xda app-developers app
I assume the OP is talking about porting an OTA Nexus S port for the NS4G
benifactor said:
There isn't even a fully functional ROM without 4g.
MMS and GPS are a problem on both ROMs. You have to have gosms to view MMS messages.
I'm starting to think we will have to wait it out until the binaries are release to aosp before we get a fully functioning rom. That will probably be awhile because the aosp guy is on vacation... or so his twitter says.
http://twitter.com/jbqueru/status/226429502182531072
Oh well. The wait continues
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Yea JBQ said he on vacation but for a few days not weeks hopefully when he gets back he can put up the binaries in AOSP! I've been asking Sprint on twitter when they going to push the update but they never answer only @sprintcare got back to me when I said I feel like it was false advertising when sprint sold the nexus devices & said the First to get Google OS updates as soon as there available well its been available & no word lol I hate cdma networks if I decided to leave I'm going T-Mobile!
Sent from my Nexus S 4G using xda premium
Killasmoke said:
Yea JBQ said he on vacation but for a few days not weeks hopefully when he gets back he can put up the binaries in AOSP! I've been asking Sprint on twitter when they going to push the update but they never answer only @sprintcare got back to me when I said I feel like it was false advertising when sprint sold the nexus devices & said the First to get Google OS updates as soon as there available well its been available & no word lol I hate cdma networks if I decided to leave I'm going T-Mobile!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Do you have proof they they ever said that? Was there an asterisk at the end of it if (and it's a big if) they did? Businesses never make commitments like that when it's out of their control.
063_XOBX said:
Do you have proof they they ever said that? Was there an asterisk at the end of it if (and it's a big if) they did? Businesses never make commitments like that when it's out of their control.
Click to expand...
Click to collapse
He, very astutely, posted the proof along with his statement. Once Google releases the ota, the decision to allow updates to the nexus devices are made completely at Sprint's discretion.