Related
From techeye:
http://news.techeye.net/mobile/google-abandons-cdma?
CDMA is marked "archived, for reference only"
http://code.google.com/android/nexus/images.html
I guess that finally nails the Verizon Galaxy Nexus as a carrier-phone. Next time buy a truly free & open device (i.e. GSM)
Seriously though. This Galaxy Nexus launch and follow-up has to be the messiest thing I've ever since Google set its foot into. From launch, to providing international release-dates, to US promotion, to handling updates, to releasing buggy updates, to pulling them, to general PR.
It's all been a big ****ing mess.
Is this the sign of the start of the end of the Nexus program or what? Or is leaving closed CDMA networks and carriers behind actually a sign of a new, better start?
Discuss.
Welcome to last week.
Sent from my Galaxy Nexus
Edit: Rootzwiki seems to have something more to offer than the techeye article.
http://rootzwiki.com/_/articles/ann...dma-galaxy-nexus-will-continue-to-update-r374
Still not crystal clear, and definitely falls under my definition of messy PR.
The rootzwiki even has an update, because Google has messed up its correcting response and needs to correct itself, again.
Yeah this is old news. Plus the 4.0.4 update is out for the VZW. What's it like beating a dead horse lol?
Sent from my Gummy Nexus
http://forum.xda-developers.com/showthread.php?t=1479199
Sent from my Galaxy Nexus
Funny thing is how the 'abandoned' device is getting more frequent updates than e officially supported device. We still don't have 4.0.3 officially yet (the last relapse is officially the Nexus S one), and 4.0.4 is CDMA only.
Welcome to last week, BTW.
Omg. Not only does it keep being reposted but by people who don't even understand what's going on and say things like " next time buy a truly free and open device".
Sent from my 'closed' 4.0.4 CDMA Galaxy Nexus.
matt30 said:
http://forum.xda-developers.com/showthread.php?t=1479199
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Hm. Should have searched the forum better it seems. I didn't find it before posting. Anyway. The conclusion from that thread still seems to be incredibly messy.
Can anyone tell WTH it now does mean to be a "Nexus" device? Ever since the release of the Galaxy Nexus and its "evil" CDMA counter-pair, that definition seems to have been in a flux.
Haesslich said:
Welcome to last week, BTW.
Click to expand...
Click to collapse
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
http://androinica.com/2012/02/cdma-...l-dev-support-updates-still-come-from-google/
Sent from my Gummy Nexus
josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
Don't talk about what you do not comprehend. That is the most ignorant thing I have heard in a long time.
I too can build 4.0.3 for CDMA. So go get educated.
adrynalyne said:
I too can build 4.0.3 for CDMA. So go get educated.
Click to expand...
Click to collapse
Good. Reading Google's various statements on the matters it seems like you cannot though, so excuse me for thinking otherwise.
So again. Yay for Google's handling of this
josteink said:
Good. Reading Google's various statements on the matters it seems like you cannot though, so excuse me for thinking otherwise.
So again. Yay for Google's handling of this
Click to expand...
Click to collapse
If my understanding is correct, you need to build 4.0.3 with the proprietary files (binaries) contained in a working cdma build of the device (what Google has called "apks"). Since those files are closed source, they cannot be included in AOSP.
Why those cdma files are closed source is a mystery. It could be for legal reasons or it could be because of the way cdma networks communicate with devices (requiring them to have a signature from the carrier embedded in them).
Sent via Galaxy Nexus
The proprietaries are all closed source. GSM included. Looks like Google couldn't obtain a license to distribute is the whole problem. Hence they also axed the factory images, because it was a form of redistribution of them as well.
adrynalyne said:
The proprietaries are all closed source. GSM included. Looks like Google couldn't obtain a license to distribute is the whole problem. Hence they also axed the factory images, because it was a form of redistribution of them as well.
Click to expand...
Click to collapse
And cmda (and I guess the proprietary software) is owned by a working group of several different telecom companies.
Sent via Galaxy Nexus
josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
how does what feel? unless you are just into foreign flags you will never use a cdma phone from verizon. looking at this logically you are either seeking attention or trolling. either way its sort of pathetic but i guess its winter over there and you havent much to do.
sahakiap said:
how does what feel? unless you are just into foreign flags you will never use a cdma phone from verizon. looking at this logically you are either seeking attention or trolling. either way its sort of pathetic but i guess its winter over there and you havent much to do.
Click to expand...
Click to collapse
At first I was trying to get some news out. And discussion about Google's general handling of the Nexus-line this time around and how it hasn't exactly been "optimal".
But I guess that got lost in everyone picking up on the snide remark rather than the rest of the comment.
josteink said:
At first I was trying to get some news out. And discussion about Google's general handling of the Nexus-line this time around and how it hasn't exactly been "optimal".
But I guess that got lost in everyone picking up on the snide remark rather than the rest of the comment.
Click to expand...
Click to collapse
Thanks for posting josteink. I hadn't seen it before either. Not sure why everyone is getting their feathers ruffled when you clearly put a smiley face beside the comment. And besides, those that are posting saying it is old news keep bumping the thread...
josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
There is no source release of 4.0.4 yet but I have been on 4.0.3 since the day I got my phone.
How does it feel? It feels great to have 32GB of space on my phone and get an average 20Mbps downstream. (At times reaching 40Mbps+)
This isn't old news at all and it is a big deal. A lot of people got screwed here by both Google and Verizon. Not having official AOSP support for developer nexus phone is unacceptable. If there were code distribution issues, then Google should have worked that out way before the official launch. I'm still holding out hope that this will be resolved, but at this point i'd settle for just getting out of my contract and moving over to the GSM variant.
On a related note, I wish CDMA would just fade away into a bad memory.
And by us , I mean those that do not have the skill or desire to hack the phone. I honestly have bought every Nexus device so that I get the latest and greatest vanilla Android experience without having to fool with it. That has been the case up until the Galaxy N.
This is the easiest phone to "hack." Make some new neural pathways; it's good for you.
Sent from my Galaxy Nexus using XDA
cant believe you're in this forum, saying those things
youre talking about a device that screams to have its bootloader unlocked in a forum that 99.990002618513226212% of the members flash all type of stuff and are willing to give u a hand
One question: Did you mean yakjuxw or yakjuwx? The builds are different I guess.
Zmydust said:
And by us , I mean those that do not have the skill or desire to hack the phone. I honestly have bought every Nexus device so that I get the latest and greatest vanilla Android experience without having to fool with it. That has been the case up until the Galaxy N.
Click to expand...
Click to collapse
Google has provided the images on their site. It is very simple to flash them to your device. No hacking required... all official methods. See the "flash" link in my post. Many of us will guide you though it if you have issues.
If that is too much "fooling around" to get "the latest and greatest", would you mind if I asked you what you are doing on a developers' site?
Sent from my Galaxy Nexus using Tapatalk 2
He's probably waiting for a direct link to the yakjuxw update...
efrant said:
Google has provided the images on their site. It is very simple to flash them to your device. No hacking required... all official methods. See the "flash" link in my post. Many of us will guide you though it if you have issues.
If that is too much "fooling around" to get "the latest and greatest", would you mind if I asked you what you are doing on a developers' site?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I guess he meant that google should provide better support for Galaxy Nexus, OTA for some and not for others makes no sense. Atleast they should provide better information. Since you see him asking here instead of an official google or an android site, then it confirms that XDA provide better answers than google and android combined.
geemaan said:
He's probably waiting for a direct link to the yakjuxw update...
Click to expand...
Click to collapse
I understand exactly what he is looking for. What I was trying to get across to him, is that it is just as easy to switch to yakju, and it comes with more benefits. No one has demonstrated any benefits to being on a non-yakju/takju build, only detriments.
amdkalban said:
I guess he meant that google should provide better support for Galaxy Nexus, OTA for some and not for others makes no sense. Atleast they should provide better information. Since you see him asking here instead of an official google or an android site, then it confirms that XDA provide better answers than google and android combined.
Click to expand...
Click to collapse
Google does provide better support for the Galaxy Nexus than any other device. Can you name me a device that Google provides better support for? If the OP is asking here on a dev site, he should expect to get a dev answer, like "flash it yourself".
What you are talking about is non-yakju builds that are NOT supported by Google - they are supported by Samsung. So, if you want to get your updates once they have gone through two bureaucracies (Samsung and Google) and double the time, then stay on a non-yakju build, If you want to get them once gone through only one (Google), then flash yakju or takju, and you will get them much sooner.
i felt the same way as the OP.. until i grew some balls and flashed to yakju. hihi.
efrant said:
... What I was trying to get across to him, is that it is just as easy to switch to yakju, and it comes with more benefits. No one has demonstrated any benefits to being on a non-yakju/takju build, only detriments....
Click to expand...
Click to collapse
I had my GNex for just 3 days before it lost completely any GSM/Data and WIFI signal - permanently!!!
I am now very happy that I didn't follow your instructions an move to "yakju", because they replaced it with a new one.
mirox3m said:
I had my GNex for just 3 days before it lost completely any GSM/Data and WIFI signal - permanently!!!
I am now very happy that I didn't follow your instructions an move to "yakju", because they replaced it with a new one.
Click to expand...
Click to collapse
If you had a faulty device, that has nothing to do with yakju.
And besides, there have been reports that people returned their non-yakju device with yakju installed, with NO issue. On the contrary, there have been NO reports (that I have seen on XDA anyway) of anyone being denied warranty because of installing yakju (which by the way, is the factory image...).
efrant said:
Google has provided the images on their site. It is very simple to flash them to your device. No hacking required... all official methods. See the "flash" link in my post. Many of us will guide you though it if you have issues.
If that is too much "fooling around" to get "the latest and greatest", would you mind if I asked you what you are doing on a developers' site?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Understandable question for sure, but I joined this forum when I was researching my first Nexus device and all roads led here. Any question could be answered here, any information found. Just because I don't dive into flashing my phone doesn't mean questions don't come up or I don't have the urge to know what's coming out or available now. Basically XDA has become my authority on cell phones even though I don't mod mine to its fullest potential.
amdkalban said:
I guess he meant that google should provide better support for Galaxy Nexus, OTA for some and not for others makes no sense. Atleast they should provide better information. Since you see him asking here instead of an official google or an android site, then it confirms that XDA provide better answers than google and android combined.
Click to expand...
Click to collapse
fpbasilio said:
i felt the same way as the OP.. until i grew some balls and flashed to yakju. hihi.
Click to expand...
Click to collapse
Touche
Another quick question, if someone local flashes my phone to Yakju , is there a way to not lose all my current data? ( texts, mms, data for the games and apps I'm currently using, etc)
Zmydust said:
Another quick question, if someone local flashes my phone to Yakju , is there a way to not lose all my current data? ( texts, mms, data for the games and apps I'm currently using, etc)
Click to expand...
Click to collapse
Yes. Given you are on 4.0.2 (or 4.0.1), you can follow this step-by-step to root. Then you can install Titanium Backup, which will back up everything for you. Then follow this step-by-step to flash yakju.
It's not difficult at all -- actually quite simple. I'm sure it looks much more daunting than it actually is.
Updates are rolled out in BATCHES. Not everyone or every firmware version receives updates at the same time. That's how it is and how it's always been.
joshnichols189 said:
Updates are rolled out in BATCHES. Not everyone or every firmware version receives updates at the same time. That's how it is and how it's always been.
Click to expand...
Click to collapse
Correct, but yakju and takju will ALWAYS get updates before the other GSM builds. Case in point: only yakju and takju are on 4.0.4, and they were on 4.0.2 first.
efrant said:
What you are talking about is non-yakju builds that are NOT supported by Google - they are supported by Samsung. So, if you want to get your updates once they have gone through two bureaucracies (Samsung and Google) and double the time, then stay on a non-yakju build, If you want to get them once gone through only one (Google), then flash yakju or takju, and you will get them much sooner.
Click to expand...
Click to collapse
still they should make nexus in a one build GSM, one build CDMA. No point of having a nexus phone that is behind in support! Atleast they should print on the box "this product is not supported by google"
Hi guys,
I currently have a Dinc2, but have been doing my due diligence in searching for a new phone. The verizon Galaxy Nexus is on my list but I'm having a hard time understanding the cdma binary package signing and it's implications for AOSP roms. Can anyone make it a little more clear for me? Or have a link that explains it in relation to the modding scene?
I'm basically wondering if it's a hinderance at all to the modding community. I see a lot of roms in the android development section, are those legit AOSP roms? Or are they modded stock roms from Verizon?
baggar11
Not a hindrance at all since the Verizon Galaxy Nexus is an AOSP device with its binaries available at Google's developer portal.
Sent from my Galaxy Nexus using Tapatalk 2
All Gnex are AOSP out of the box, the VZW version just has the VZW app added.
What was all this hoopla about then? Sounds like Verizon was making it hard for Google and the community to support the cdma Nexus's. Is that stuff pretty much resolved, or was it never really a problem for the community? Thanks for the reply guys!
http://pocketnow.com/2012/07/10/gal...p-support-with-jelly-bean-but-not-for-sprint/
CDMA devices have been a thorn in the side of the AOSP for some time now. Google explained the issues at hand when it made a statement back in February, pointing out how the need for carrier-signed binaries containing critical communications code was getting in the way of developers being able to build Android for these devices. Luckily, things started looking up just last week, with new binaries becoming available for the Nexus S 4G on Sprint. At the time, the situation still looked bleak for the Verizon Galaxy Nexus. A week later, the tide has really turned, and last night’s publication of the Android 4.1 Jelly Bean source saw the arrival of some eagerly awaited binaries for the VZW GNex. Where are the equivalent files for the Sprint GNex, though?
WiredPirate said:
All Gnex are AOSP out of the box, the VZW version just has the VZW app added.
Click to expand...
Click to collapse
Sprint version is not supported by AOSP, as of yet.
As the the title suggests, I think that it would help make things less cluttered. Just a Nexus 7 LTE (2013) Android Development subforum, not a complete new device forum. Btw, I still don't understand the difference between Development and Original Development, so please comment if you do understand and do think that we need them both for LTE version.
I already suggested this to forum mod MikeChannon, he said they would consider it.
Thinking that the earlier we get it the less effort, problems and trouble it creates I am now putting up this poll.
kendong2 said:
As the the title suggests, I think that it would help make things less cluttered. Just a Nexus 7 LTE (2013) Android Development subforum, not a complete new device forum. Btw, I still don't understand the difference between Development and Original Development, so please comment if you do understand and do think that we need them both for LTE version.
I already suggested this to forum mod MikeChannon, he said they would consider it.
Thinking that the earlier we get it the less effort, problems and trouble it creates I am now putting up this poll.
Click to expand...
Click to collapse
That would be a good idea. And you can read about it here http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
Sent from my Nexus 7 (2013) using Tapatalk 4
Nexus 7 LTE different
The Nexus 7 LTE is different from Nexus Wi-Fi similarly how the predecessor Nexus 7 Mobile is different from the Wi-Fi model.
However, in the US, the LTE will run on the top-3: AT&T, Verizon and T-Mobile, and in multiple modes, so expect lots of questions about APNs, plans and such.
Another area of confusion will be the various VoIP clients people will use, like Talkatone, Sipdroid, CSipSimple.
I am not sure how it affects the forum disposition, but if you thought you didn't have enough impossible problems before, get yourself a shiny Nexus 7 LTE... There's a reason for it being late.
PhoneGeek said:
I am not sure how it affects the forum disposition, but if you thought you didn't have enough impossible problems before, get yourself a shiny Nexus 7 LTE... There's a reason for it being late.
Click to expand...
Click to collapse
not sure what you are implying here, but i have one for almost a week now, it is awesome, and it is flawless. even stock 4.3 rooted is not that bad, i would like to have some options though.
It's been announced that all operator versions will be identical (ATT, Sprint, Verizon, etc.). That is something different from the previous N7. So maybe, just maybe someone should try ROM compatibility with Flo (Wifi). If that works out (minus LTE hardware drivers) we won't need a separate forum. And the development would be much better in total as a result of having way more devices....it'd be cool to pick a WiFi rom and flash it on an LTE, and then just flash the LTE module...oh the possibilities....
i tried different flo images on my deb n7 and it doesn't work. it's not booting, it gets stuck at the x. only way to make it work again was flashing an deb image again. so i think a sub forum for deb would be nice
Yeah, good idea. The old Nexus 7 has a dedicated sub-forum for the 3G version too. It makes finding stuff much easier.
Nexus 7 LTE
kendong2 said:
not sure what you are implying here, but i have one for almost a week now, it is awesome, and it is flawless. even stock 4.3 rooted is not that bad, i would like to have some options though.
Click to expand...
Click to collapse
I am referring to the Nexus 7 LTE having a seven-band LTE radio. It's the first device anytime, anywhere I know of to have such a complex radio.
I am also referring to the enormous possibilities this offers Nexus 7 LTE owners, which will compel them to try things never tried before. Take the tinkering with a Galaxy Nexus. Now triple it.
---------- Post added at 12:12 PM ---------- Previous post was at 11:37 AM ----------
Apparently the Nexus 7 LTE went on sale over-the-counter in Germany and Australia on 8/29:
Asutralia: http://www.ozbargain.com.au/node/114844
Germany: https://www.youtube.com/watch?v=iZ0iXzQNckI
Note that there are two versions with different LTE bands.
The EU model is for everywhere outside the US, which would be 95% of the world's telecom. "EverUwhere"
So Google/ASUS launches the US model after the EU model.
Apparenly ASUS has a 16 GiB LTE model that Google isn't selling yet https://en.wikipedia.org/wiki/Nexus_7_(2013_version)#Model_variants
well, i guess this means searching for us LTE owners then...
kendong2 said:
well, i guess this means searching for us LTE owners then...
Click to expand...
Click to collapse
I got an LTE model in Europe on 2 Sept, and I really would like to have a sub-forum, since browsing the normal one and trying to find stuff for the LTE one is just driving me crazy.
Actually, you can find this device in Europe (Germany and Italy, maybe Poland or Romania but I'm not sure).
And we wait soon this version in UK and France nearly.
And it's my next device
And as you know you can request to open this subforum as N7 3G here: *** New Device Forum Requests ***
This would be a great idea. Keep the wifi only and LTE ROMs in different sections.
Sent from my SAMSUNG-SGH-T999 using xda app-developers app
Good idea. Otherwise, I'll need to constantly remind myself to be mindful if the ROM or update is for the wifi only, or LTE.
Otherwise, another possible option would be to append the beginning of each post with a [WIFI] , [LTE] or [GENERIC] depending on which flavour it belongs to.
philos64 said:
Actually, you can find this device in Europe (Germany and Italy, maybe Poland or Romania but I'm not sure).
And we wait soon this version in UK and France nearly.
And it's my next device
And as you know you can request to open this subforum as N7 3G here: *** New Device Forum Requests ***
Click to expand...
Click to collapse
Forum for the device is already created, we just need a subforum for LTE version, pretty basic considering the old model got one as well! Why they didn't create it at the start is a mystery to me.
jak3z said:
Forum for the device is already created, we just need a subforum for LTE version, pretty basic considering the old model got one as well! Why they didn't create it at the start is a mystery to me.
Click to expand...
Click to collapse
Sorry, but you have not understood what I meant or I misspoke.
I meant that it would be better to use the normal way to request the opening of a sub-forum in the thread provided for it => *** New Device Forum Requests ***
I know that the forum, for this device, has been created and we have use the normal way to open a sub-forum for the N7 3G.
I know that the admins will open a sub-forum 2013 N7 for LTE very soon. Don't be afraid
philos64 said:
Sorry, but you have not understood what I meant or I misspoke.
I meant that it would be better to use the normal way to request the opening of a sub-forum in the thread provided for it => *** New Device Forum Requests ***
I know that the forum, for this device, has been created and we have use the normal way to open a sub-forum for the N7 3G.
I know that the admins will open a sub-forum 2013 N7 for LTE very soon. Don't be afraid
Click to expand...
Click to collapse
I don't lose anything posting, true, just did it.
Muikkuman said:
That would be a good idea. And you can read about it here http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
Sent from my Nexus 7 (2013) using Tapatalk 4
Click to expand...
Click to collapse
thanks for the hint. so basically the (not-original) development forums are the useless ones, that could as well be deleted all together. or stuff that is OK and useful, but on an arbitrary scale not "original" enough.
so basically i have to look in both subforums all the time to find something interesting. way to go, xda. and i thought they were back on a better path...
bumping this...
kendong2 said:
bumping this...
Click to expand...
Click to collapse
Forum mods or whoever have to do it, seem to be too busy for it.
Hello,
I have a question on what is needed by developers to make Lollipop ROMs for our S3.
I have been following the releases and know that the images for the Nexus devices are up and that OTAs have begun. Is that what developers need as a starting point?
As you can tell I'm fairly clueless about this so I appreciate any information because I like to follow along.
Thanks!
Devs need the actual sources to build, which have been released. Unfortunately they can't work with the factory images for Nexus devices.
If I remember correctly, it took 2 or 3 months to get a usable KitKat build from Slim. (the first ones to do it, I recall.) We'd be lucky to see it by the new year, in my opinion.
Thank you for the info.
So they take the Nexus sources and then build it for our devices and then figure out how to add drivers for our hardware, etc?
Thank you for the timeline. I'm hoping it will be sooner, but your estimate is more realistic
I saw this in the S3 international forum:
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-namelessrom-t2939673
And
http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Looks like they are hard at work on lollipop for their devices. I wonder if anyone is working on it for ours yet?
philhouse said:
I saw this in the S3 international forum:
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-namelessrom-t2939673
And
http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Looks like they are hard at work on lollipop for their devices. I wonder if anyone is working on it for ours yet?
Click to expand...
Click to collapse
Im wondering the same and if anybody has taken interest in building it for the d2lte variants like the att etc..
I haven't seen anything yet in the forums, but I'm still hopeful that someone will!
Found this today. Sweeeeet:
http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
philhouse said:
Found this today. Sweeeeet:
http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Click to expand...
Click to collapse
Yeah I been on the ROM since it was provided.