Related
Still haven't got mine. I have the samsung build (forgot what the code is yakjuw?)
Anyways, I really hope we get the updates everyone else is getting because I'm not going to flash to stock google build just to get updates.
I have the samsungbuild (yakjuxw) and i haven't got it yet (norway)
Well I sure hope we get it. That was one of my worries when an XDA forum member first found out there were different builds. Hope we still get updates quickly like the google ones.
I haven't gotten it yet on my yakjuux.
Is 402 for GSM or LTE? I thought it was LTE only.
aldo37 said:
Is 402 for GSM or LTE? I thought it was LTE only.
Click to expand...
Click to collapse
I have it and I am on GSM.
Am on Google build and still ain't got it?
Sent from my Galaxy Nexus using XDA App
aldo37 said:
Is 402 for GSM or LTE? I thought it was LTE only.
Click to expand...
Click to collapse
It is for both
brian85 said:
Well I sure hope we get it. That was one of my worries when an XDA forum member first found out there were different builds. Hope we still get updates quickly like the google ones.
Click to expand...
Click to collapse
We will get it, but those sent from Google will get it everything from 1 day to 1-2 weeks before us i've heard.
They are planing to release 4.0.3 soon too, so we should get 4.0.2 maybe tomorrow if we are luckey.
aldo37 said:
Is 402 for GSM or LTE? I thought it was LTE only.
Click to expand...
Click to collapse
Both. But the OTA for GSM started happening today and LTE had the 4.0.2 OTA happening yesterday.
The stock image files were released for both (4.0.2) yesterday.
Anyone yet?
Also, does anyone know if Google responded about this? We have a nexus...we should get updates fast and first like everyone else. Ridiculous.
Article posted on Android Central about the app the person developed. The "update" at the bottom of the article sheds some light.
http://www.androidcentral.com/app-t...-your-galaxy-nexus-cant-tell-you-whether-care
zephiK said:
Both. But the OTA for GSM started happening today and LTE had the 4.0.2 OTA happening yesterday.
The stock image files were released for both (4.0.2) yesterday.
Click to expand...
Click to collapse
For both types but Google builds, no image files for Samsung builds afaik.
Sent from my Galaxy Nexus using xda premium
My GSM Gnex came with Samsung build and I didn't get v4.0.2 since yesterday. That's why I flashed to yakju. Loving it so far!
kwurky said:
My GSM Gnex came with Samsung build and I didn't get v4.0.2 since yesterday. That's why I flashed to yakju. Loving it so far!
Click to expand...
Click to collapse
+1 easy step, no problems at all
Sent from my Galaxy Nexus using xda premium
Anyone yet?
Sent from my Galaxy Nexus using XDA App
rdy2go said:
+1 easy step, no problems at all
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
How did you so it? Do i need root?
Talking about desperation... lol just wait a little more
Btw. What app do I use to know my build?
Sent from my Galaxy Nexus using Tapatalk
@ajftl There's this nice little app in the market called GN Official Update Checker that tells you your build and if it's updated directly by Google.
Link: http://androidcommunity.com/official-galaxy-s-ii-ics-upgrade-could-come-march-1st-20120210/
Let's hope this is true.
Yeah not us anytime soon. This is talking about the international version.
Sent from my Transformer TF101 using Tapatalk
Thats not for us its for international .. Wont even help us.
dtm_stretch said:
Yeah not us anytime soon. This is talking about the international version.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Kernel sources? I thought we needed those. The international version as it stands now runs fine on my phone.
seeing as the international is a gsm phone, wouldn't the kernel sources be sufficiently different from our phone so as not to work? Never messed with kernels before, so sorry if it's a stupid question.
agentfazexx said:
Kernel sources? I thought we needed those. The international version as it stands now runs fine on my phone.
Click to expand...
Click to collapse
You flashed international version on your phone? Or did I read this wrong... sorry if I did
playya said:
You flashed international version on your phone? Or did I read this wrong... sorry if I did
Click to expand...
Click to collapse
Yeah, the version off of sgs2ics.com. Booted fine.
darthstewie said:
seeing as the international is a gsm phone, wouldn't the kernel sources be sufficiently different from our phone so as not to work? Never messed with kernels before, so sorry if it's a stupid question.
Click to expand...
Click to collapse
Kernel sources for everything not related to ril would help us, so Wifi, BT, GPS, etc. Since we already have 3g and SMS working, my guess is that the kernel source for the int'l SGS II could round out what we need to get an acceptable working ICS ROM.
darthstewie said:
seeing as the international is a gsm phone, wouldn't the kernel sources be sufficiently different from our phone so as not to work? Never messed with kernels before, so sorry if it's a stupid question.
Click to expand...
Click to collapse
Not entirely. The radio sources would be, yes, but the hardware drivers are the same (so stuff to get the camera and whatnot working could be used) as our phone, I think.
kiekan said:
Not entirely. The radio sources would be, yes, but the hardware drivers are the same (so stuff to get the camera and whatnot working could be used) as our phone, I think.
Click to expand...
Click to collapse
All of the drivers work for hardware (minus radio, wifi worked).
Either way, if Samsung is releasing it, chances are Sprint will take this and act on it.
agentfazexx said:
Yeah, the version off of sgs2ics.com. Booted fine.
Click to expand...
Click to collapse
I call BS on this one...
Sent from my SPH-D710 using xda premium
agentfazexx said:
Either way, if Samsung is releasing it, chances are Sprint will take this and act on it.
Click to expand...
Click to collapse
Oh if only this were true. You are new to Sprint aren't you...
squiggie said:
I call BS on this one...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Okay. Well I know it booted fine. Try it yourself. Otherwise, shut up and stop trolling.
boe said:
Oh if only this were true. You are new to Sprint aren't you...
Click to expand...
Click to collapse
6 months into a contract.
agentfazexx said:
All of the drivers work for hardware (minus radio, wifi worked).
Either way, if Samsung is releasing it, chances are Sprint will take this and act on it.
Click to expand...
Click to collapse
Samsung already stated they will be having updates by the first quarter for some devices like the SGS2 , but in the end it's up to the carriers and Sprint loves to drag it out.
Sent from my SPH-D710 using xda premium
agentfazexx said:
Okay. Well I know it booted fine. Try it yourself. Otherwise, shut up and stop trolling.
Click to expand...
Click to collapse
People have been having issues booting back to stock or anything else for that matter. May I ask have you nandroid back to anything since booting it up? Also does your pc recognize your phone?
I wouldn't expect Sprint to have a Release of ICS for the Epic Touch until late Summer or early Fall 2012. By then, the phone will be almost 1 year old and Sprint will start saying the ET4G is "End of Life" and stop supporting it altogether.
-Daryel
playya said:
People have been having issues booting back to stock or anything else for that matter. May I ask have you nandroid back to anything since booting it up? Also does your pc recognize your phone?
Click to expand...
Click to collapse
Had to flash another kernel then nandroid back to get back to 2.3. Didn't try plugging it into my PC.
daryelv said:
I wouldn't expect Sprint to have a Release of ICS for the Epic Touch until late Summer or early Fall 2012. By then, the phone will be almost 1 year old and Sprint will start saying the ET4G is "End of Life" and stop supporting it altogether.
-Daryel
Click to expand...
Click to collapse
Fortunately for us, we don't have to rely on Sprint, as Samsung will release the kernel sources we need to get where we need to go. Also, the 4.0 iteration we would get from Sprint would be TouchWiz'd up, which for me I could care less about. We will have daily-driver quality CM9 and AOSP ICS well before we see an official ICS-based ROM released by Sprint.
And before you ask, yes I have been with Sprint for a long time, and yes I came from the OG Epic 4g.
playya said:
People have been having issues booting back to stock or anything else for that matter. May I ask have you nandroid back to anything since booting it up? Also does your pc recognize your phone?
Click to expand...
Click to collapse
The people doing it are Odin a tar and its bricking them because they don't know what they are doing....you can use the tar file with mobile Odin pro and retain root which will allow you to use mobile Odin to flash kernel with cwm to get out of the brick but without root can't use mobile Odin...you can take the tar apart and make a ROM out of it...as long as the bootloader and radio is not in there you should be good
Sent from my SPH-D710 using xda premium
The Galaxy Nexus phones I bought of Google Play all got the 4.1.2 update... but the freebie phone I got when I attended Google IO still hasn't. Are the updates still rolling out or is something wrong here? Keep checking, but it never finds an update.
Android version
4.1.1
Baseband version
I9250XXLF1
Kernel version
3.0.31-g6fb96c9
[email protected] )
#1 SMP PREEMPT Thu Jun 28 11:02:39 PDT 2012
Build number
JRO03C
if your device is the same as the retail version then just manually flash the the update. You can download the image from Googles site.
Problem solved
Sent from my Galaxy Nexus
Root it and boot it
Sent from my Galaxy Nexus using xda app-developers app
b1337 said:
Root it and boot it
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think the point he is making is that everyone got the update while he is left in the dark, and he is one of the few that probably deserves the update first before others
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
b1337 said:
Root it and boot it
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What has rooting got to do with getting updates?
harveydent said:
What has rooting got to do with getting updates?
Click to expand...
Click to collapse
Toot it and root it
Sent from my Galaxy Nexus using xda app-developers app
I havent gotten the update yet either so i ended up flashing it
i do live in new zealand though which is pretty remote in terms of cell phones
we dont even have galaxy nexus's here im like the only one
matistight said:
I think the point he is making is that everyone got the update while he is left in the dark, and he is one of the few that probably deserves the update first before others
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I understood his post as what you had suggested, but I also felt compelled to point him into a direction that could get him current with everyone else if he chose to do so......basically I circumvented reasoning and gave a possible solution for him to mind juggle
Sent from my Galaxy Nexus
confirmed. no update on my IO gnex either. wtf?
you are on xda.. download the toolkit, unlock bootloader and flash recovery on your gnex, download a rom/gapps and put it on your sd, flash the rom/gapps = problem solved
The point is not that he wants the update... its that Google has not pushed the update to the IO devices.
Sent from my Galaxy Nexus using Tapatalk 2
Kennnny1 said:
The point is not that he wants the update... its that Google has not pushed the update to the IO devices.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well he may be waiting a very long time as IO devices are generally the very last to be updated.
Sent from my Galaxy Nexus
If I have to flash it, eventually I will. I wanted to keep this as my stock dev device for development and would've expected that the devices given to the developers at Google IO wouldn't be receiving the updates late... assuming that this thing will get an update at sometime in the future. Very surprising since I would've thought the phones handed to devs, if any, should be first in line to receive updates, unless something has gone wrong with my update.
Zoonsf said:
If I have to flash it, eventually I will. I wanted to keep this as my stock dev device for development and would've expected that the devices given to the developers at Google IO wouldn't be receiving the updates late... assuming that this thing will get an update at sometime in the future. Very surprising since I would've thought the phones handed to devs, if any, should be first in line to receive updates, unless something has gone wrong with my update.
Click to expand...
Click to collapse
Sorry to hear it. I fully agree but I think Google view is that it is a dev device so you can update with the 4.1.2 firmware currently available. Send Google an email and see what they say.
Good luck...
Sent from my Galaxy Nexus
Well, I called Samsung and they said it was the carrier's responsibility. Uh, what carrier? This is a GSM phone that's not from T-Mobile. Weird, I figure their staff just can't handle the question. I get the number for their "expert" support. He says to talk to Google.
I hunt the contact number for Google devices and get a nice guy who has me turn on airplane mode, then turn on wifi. Then clear data for Google app services. Check the about settings, last update check was in 1969. <sigh>, yes, I've done this, but I'll try again. No update found.
He said that it was strange. The update should've been pushed out to it by now and something was wrong, but couldn't help. The only thing left to do was to ship it to Samsung and have them flash the ROM on it.
Forget that, I gave up and I flashed the 4.1.2 factory image myself. I guess I could've saved myself some time by doing it in the first place, but I'm still curious and would like to know why I got the 4.1.1 OTA but 4.1.2 didn't work. Weird.
FYI, my IO nexus just got the update to 4.1.2 today, almost a full month after it started rolling out.
I recently received the JDQ39 OTA on my GNEX test phone. Oldblue910 will provide the community with the most recent boot loader version, kernel version and baseband version.
Thank you once again for breaking the news to us! How do the new radios seem to be working so far?
Sent from my Galaxy Nexus using Tapatalk 2
ntb81 said:
Thank you once again for breaking the news to us! How do the new radios seem to be working so far?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The radios appear to be working really well.
How is the battery life looking on this build?
Great to hear. Looking forward to the new radios!
Sent from my Galaxy Nexus using Tapatalk 2
Thank you!!
Not gonna ask for a specific ETA but was just wondering how long a process it is to extract the radios. Again, I am fine with however long it may take and do not need a time that they will be posted. Just wondering if it's something that can be done quick for you guys or if it will take awhile.
Nephilim said:
Not gonna ask for a specific ETA but was just wondering how long a process it is to extract the radios. Again, I am fine with however long it may take and do not need a time that they will be posted. Just wondering if it's something that can be done quick for you guys or if it will take awhile.
Click to expand...
Click to collapse
I would like to know as well i don't think its out of the park to ask
Sent from my Galaxy Nexus using Tapatalk 2
obviously not an official answer, but it seems that they cannot extract the radio from the phone, and so they are reverting to 4.1 and hoping that he gets the OTA again so they can extract it before the ota is flashed?
Sounds like that is the plan. But this raises a good point, especially since we don't know how the test ota process works, and thus don't know for sure that he would receive the ota again. Maybe it would make sense to first get it rooted and then pull the radios via the gnex toolbox (which is probably easier and quicker than doing it manually) and maybe also pull a full system image or create an image. zip of the stock ROM through CWM.
That said, these guys are doing this out of pure goodwill, and they should do whatever works best for them and doesn't interfere with their lives. Just happy they gave us the news
Sent from my Galaxy Nexus using Tapatalk 2
Awesome man, patiently waiting . thank you for this
Sent from my Galaxy Nexus using Tapatalk 2
ntb81 said:
Sounds like that is the plan. But this raises a good point, especially since we don't know how the test ota process works, and thus don't know for sure that he would receive the ota again. Maybe it would make sense to first get it rooted and then pull the radios via the gnex toolbox (which is probably easier and quicker than doing it manually) and maybe also pull a full system image or create an image. zip of the stock ROM through CWM.
That said, these guys are doing this out of pure goodwill, and they should do whatever works best for them and doesn't interfere with their lives. Just happy they gave us the news
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Agree. I figured there had to be a reason this doesn't work, or else this is clearly the best option since he might never get the OTA again after reverting! :good:
Awesome work fella's. Truly awesome.
ntb81 said:
Sounds like that is the plan. But this raises a good point, especially since we don't know how the test ota process works, and thus don't know for sure that he would receive the ota again. Maybe it would make sense to first get it rooted and then pull the radios via the gnex toolbox (which is probably easier and quicker than doing it manually) and maybe also pull a full system image or create an image. zip of the stock ROM through CWM.
That said, these guys are doing this out of pure goodwill, and they should do whatever works best for them and doesn't interfere with their lives. Just happy they gave us the news
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The OTA "should" be linked to a device ID. When the public OTA rolls out, blocks of devices are updated at various intervals (which is why some get the OTA later than others). The server housing the OTA at present should have a block of test device IDs authorized to download. If this holds true, then he should be able to grab the update again if running JRO03O. Key word is "should". :fingers-crossed:
Most of the Roms out 4.2.2. not working for me
El Madhatter said:
The radios appear to be working really well.
Click to expand...
Click to collapse
I've tried quite a few New roms 4.2.2. and tried out by calling my home land line and letting it stay connected and always around 29 to 30 mins it always drops ......But i switched back to 4.2.1 and it works fine ..."stable"
meteriso said:
I've tried quite a few New roms 4.2.2. and tried out by calling my home land line and letting it stay connected and always around 29 to 30 mins it always drops ......But i switched back to 4.2.1 and it works fine ..."stable"
Click to expand...
Click to collapse
Odd. I'm running a self built 4.2.2, and I just finished a 1.5 hour call with no issue.
Sent from my Galaxy Nexus using Tapatalk 2
We're getting 4.2.2? Really? Looks to me like the monkeys have finally flown out of Mead's ass...
Sent from my Nexus 10 using xda app-developers app
Hearing this news made my morning! 4.2.2 and new radios!? :highfive:
yea
trestevenson said:
Hearing this news made my morning! 4.2.2 and new radios!? :highfive:
Click to expand...
Click to collapse
Hearing its stable its released and the radios are an improvement will make mine....
Winesnob said:
The OTA "should" be linked to a device ID. When the public OTA rolls out, blocks of devices are updated at various intervals (which is why some get the OTA later than others). The server housing the OTA at present should have a block of test device IDs authorized to download. If this holds true, then he should be able to grab the update again if running JRO03O. Key word is "should". :fingers-crossed:
Click to expand...
Click to collapse
We are still working out some driver issues.
I've been scanning the forums for the GS3 to see if anything were to come up for the LTE version of the GS3. Apologies if i missed it, but I had to ask.
The leaked schedule said it would be available 11/25, only to have the T999 get access to it, then the T999v got it. Where's ours?
Be happy you don't have troubles like the Verizon users have.
The LTE version is bricking phones so has been rolled back.
Perseus71 said:
Be happy you don't have troubles like the Verizon users have.
The LTE version is bricking phones so has been rolled back.
Click to expand...
Click to collapse
I guess that's good. I wonder what the problem is with this. Something with the radio that didn't affect the T999 and v variants?
shahp said:
I guess that's good. I wonder what the problem is with this. Something with the radio that didn't affect the T999 and v variants?
Click to expand...
Click to collapse
No Clue. I see that as a poorly tested upgrade pushed out in a hurry.
If the 4.3 update is being pushed back for better testing and bug fixes then I'm all for that. If it's pushed back for particularly good reason, no improvements, and we still get bugs the others are having then I'll be kinda pissed.
Sent from my SGH-T999L using xda app-developers app
Thank Me Later said:
If the 4.3 update is being pushed back for better testing and bug fixes then I'm all for that. If it's pushed back for particularly good reason, no improvements, and we still get bugs the others are having then I'll be kinda pissed.
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
Even the Regular T999 users who did get that update aren't thrilled either. So have no fear.