Related
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
I for one is not counting on it, frankly...
No matter how beautifully you phrase things, WE GOT NOTHING YET.
Sent from my SGH-T989 using XDA App
[A virgin sacrifice] =
SO FREK'IN EXCITED!!!!!
thanks for the info bro looking forward to it
jessejames111981 said:
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
Click to expand...
Click to collapse
the thing is, many of those are KANGed as in not officially supported by CM team
of the few that officially are supported is Nexus S i9020 and SGS i9000
even the "classic" SGS2 i9100 is not fully supported by CM yet, there's more bugs than... well it's not usable as a daily driver
that was just before the end of last year
they might have improved it a bit by now
even the Nexus S version of CM9 is still very buggy, that's why i have the stock official ICS4 instead on my Nexus S
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
iwasblown said:
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't believe in idiots, can you make them all go away?
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Why this statement?
From a glaxay better than yours.
tl;dr
I am basing my entire post on the fact that Steve Kondik has our device and should theoretically be working on it.
Click to expand...
Click to collapse
Steve Kondik aka Mr. Cyanogen also works for Samsung. I am sure he gets ALL Samsung devices...
corwest said:
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Click to expand...
Click to collapse
It only takes 2 weeks to modify the stock rom or cm7/9.
Its the expectation that is built when people act like quantity is all that matters. There are basically only 2 people making roms; Samsung and CM team, everyone else just waits on these 2 so that they could tweak and modify one of those 2. The funniest part is that the use of the word "kanging" is thrown around among these other people.
housecat93 said:
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
Click to expand...
Click to collapse
I'd like to believe, I really would. And I hope this does come to fruition. However, even if it doesn't, the few ROMS we do have are pretty good, and our phone still outperforms almost anything else available right now, so I'll still be happy.
I do have one request, though. Can we figure out a way to make CM based ROMS happen without a virgin sacrifice? There are so many other things in life that require those, that they are starting to become scarce
The fact that lots of other phones have alphas and repositories available to even make kangs does not fare well for our device.
Sent from my HTC_Amaze_4G using xda premium
guys chillax..slayher already has it booting..and that's news from december
good to know, thanks
Great phone, needs more dev time and hopefully that comes along with it when ics hits.
We got shafted early with the nexus release so close to the T989 and a dev that promised things but ran away.
New year brings new hope. Great respect for the devs that care about our phone.
Sent from my SGH-T989 using XDA App
Let's hope the mods don't ban what little devs we have left...
Sent from my HTC_Amaze_4G using xda premium
AznDud333 said:
guys chillax..slayher already has it booting..and that's news from december
Click to expand...
Click to collapse
I don't follow, what do you mean by booting?
synergeticink said:
I don't follow, what do you mean by booting?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Booting
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"
I downloaded the Galaxy Nexus ToolKit the other day and I noticed that under CDMA/LTE Verizon model, after the latest ICS build that I know of for The VZW GN (IMM76k) there is a 4.1 Build JRN84D listed...I looked that build up and it's JB for the Nexus 7 apparently? This confuses me, because I'm pretty sure that the Nexus 7 has drastically different hardware in contrast to the Galaxy Nexus and this Toolkit is apparently SPECIFIC to the Galaxy Nexus (I mean...it's in the name). So why is there a JB build listed in this toolkit for the Nexus 7 UNDER the MYSID-TORO section?
I've one more question as well; before you can even being using the ToolKit it asks you to choose which Model and Build you have. My phone is currently on the Vicious JB 4.1 v5 build and that's not something I'm able to choose. Does that mean I need to go back to stock before I can use this toolkit?
Thanks!
Bump, because it is been a day or so. Or maybe more? I lose track of time sometimes
Sent from my Galaxy Nexus using xda app-developers app
dont use a toolkit.
there is no official JB for the verizon GN.
I'm really not trying to sound like an ass, but you answered two questions that I did not ask. I never asked if I should use a tool kit or not, nor did I ever imply that I thought there was an official verizon wireless jelly bean released yet , and I certainly didn't ask if one existed.
I apologize if there was a misunderstanding, I did not mean to make any misleading remarks or comments.
Sent from my Galaxy Nexus using xda app-developers app
Don't use toolkit
Its pretty simple answer that though don't answer your question but answer to your problems that you might get later.
Soundfx4 said:
I'm really not trying to sound like an ass, but you answered two questions that I did not ask. I never asked if I should use a tool kit or not, nor did I ever imply that I thought there was an official verizon wireless jelly bean released yet , and I certainly didn't ask if one existed.
I apologize if there was a misunderstanding, I did not mean to make any misleading remarks or comments.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm not trying to sound like an ass, but to answer your last question in post #1, no you do not. However, it is obvious that the toolkit is showing you wrong info, so would you trust it? I wouldn't. So, as the others have said, don't use a toolkit. Flash things manually.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I'm not trying to sound like an ass, but to answer your last question in post #1, no you do not. However, it is obvious that the toolkit is showing you wrong info, so would you trust it? I wouldn't. So, as the others have said, don't use a toolkit. Flash things manually.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I need to apologize; I honestly was not trying to being hostile, I was just pointing out the fact that my questions were not answered, and in fact, information that I didn't request was given instead. I didn't intend to inspire anyone to feel that they need to retaliate, but I will admit, it is very frustrating when I start a thread asking, for example, "why are some apples red, and some green?" And instead of someone answering my question, they advise me not to eat apples. Surely you can see why this would be frustrating? I really don't want to be an ass to anyone because I'm anything but an ass, but at the same time, I feel need to point out the irrelevancy of the response. And I try to do it without being a rude about it. Hence the, "i'm not trying to sound like an ass" part, which was obviously taken offensively, because you used it deliberately with the intent of snapping back at me when I never snapped at anyone in the first place.
So I do apologize, and this is not sarcasm, nor me being a smart ass, I really am apologizing for upsetting anyone. There's just no reason for it, and I certainly do not intend to upset anyone.
Soundfx4 said:
I need to apologize; I honestly was not trying to being hostile, I was just pointing out the fact that my questions were not answered, and in fact, information that I didn't request was given instead. I didn't intend to inspire anyone to feel that they need to retaliate, but I will admit, it is very frustrating when I start a thread asking, for example, "why are some apples red, and some green?" And instead of someone answering my question, they advise me not to eat apples. Surely you can see why this would be frustrating? I really don't want to be an ass to anyone because I'm anything but an ass, but at the same time, I feel need to point out the irrelevancy of the response. And I try to do it without being a rude about it. Hence the, "i'm not trying to sound like an ass" part, which was obviously taken offensively, because you used it deliberately with the intent of snapping back at me when I never snapped at anyone in the first place.
So I do apologize, and this is not sarcasm, nor me being a smart ass, I really am apologizing for upsetting anyone. There's just no reason for it, and I certainly do not intend to upset anyone.
Click to expand...
Click to collapse
To follow along with your apple analogy: if you are asking why some apples are red and why some are green so you can figure out which ones are better to to eat, and someone tells you those apples are rotten, don't eat them, does it matter why some are red and some are green? It becomes purely an academic exercise. Unless you weren't asking the question to find out which one was better to eat, but just purely out of curiosity in the first place.
So, if that is the case, here are the answers to your questions:
Soundfx4 said:
I downloaded the Galaxy Nexus ToolKit the other day and I noticed that under CDMA/LTE Verizon model, after the latest ICS build that I know of for The VZW GN (IMM76k) there is a 4.1 Build JRN84D listed...I looked that build up and it's JB for the Nexus 7 apparently?
Click to expand...
Click to collapse
There is a JRN84D build for maguro (GSM GNex), although there is no JRN84D build for toro.
Soundfx4 said:
This confuses me, because I'm pretty sure that the Nexus 7 has drastically different hardware in contrast to the Galaxy Nexus and this Toolkit is apparently SPECIFIC to the Galaxy Nexus (I mean...it's in the name).
Click to expand...
Click to collapse
Yes, the Nexus 7 has different hardware than a GNex. You are confused because you did not understand that JRN84D can be for different devices... although a maguro JRN84D build is different than a nakasi JRN84D build, but they are still JRN84D builds.
Soundfx4 said:
So why is there a JB build listed in this toolkit for the Nexus 7 UNDER the MYSID-TORO section?
Click to expand...
Click to collapse
It is not a build for the Nexus 7, as mentioned above.
It is listed under mysid-toro because it is a MISTAKE/ERROR. <== This is why you should not use toolkits. Toolkits that are made to cover multiple builds and devices are more prone to having mistakes and incompatibilities. And, as with anything that uses scripts made by someone else, you do not know what it is doing so if something messes up, good luck trying to figure it out (given that you do not have the knowledge to flash things yourself without scripts).
Soundfx4 said:
I've one more question as well; before you can even being using the ToolKit it asks you to choose which Model and Build you have. My phone is currently on the Vicious JB 4.1 v5 build and that's not something I'm able to choose. Does that mean I need to go back to stock before I can use this toolkit?
Click to expand...
Click to collapse
You are asking this question because you do not know what the toolkit is doing. <== Another reason not to use them. I would hazzard a guess that it is asking which version of android your ROM is based on. So if Vicious JB 4.1v5 is based on JRN84D, then that is probably what the toolkit is looking for (so that it can boot the right kernel or something), but that is just a guess.
Flashing images, etc. is not difficult at all. But, if you don't want to take a few minutes to learn, you will likely have additional issues in the future using toolkits.
http://forum.xda-developers.com/showthread.php?t=1469909
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.