Have had my nexus now for several months. Its a uk simfree direct from amazon.co.uk. yakju, gsm, Its stock, un rooted.
Originally it was running 4.0.2 and ran perfectly. But since the it picked up the 4.0.4 ota update (just after the release) i get freezing and random reboot issues while its in standby (never happens when i am using it). After reboot there is often a hole in my battery log (see attached pic).
The freezing is a big issue has i have to take out the battery to bring it back to life.
If this is a common issue then i will stick with it, but if not them i will have to return it. I don't want to root or load an alternative rom because i don't think i should have to just to get a reliable phone.
I have removed most of my apps to see if that helps, but i didn't have that many anyway and most of those are google own.
I would appreciate thoughts!
Sent from my Galaxy Nexus using xda premium
i have a samsung galaxy nexux with 4.0.4, too and it works perfect. it sounds like a hardware defect for me..
No other opinions?
Sent from my Galaxy Nexus using xda premium
Easiest way to find out if it is hardware related, is to start from scratch: flash the factory image and see if you still have the freezing. If not, it is some app or some setting you changed. If you still have the freezing, it's probably hardware related.
Well since i had jelly bean ota, no freezing or reboots :thumbup:
/touchwood
Sent from my Galaxy Nexus using xda premium
I feel better after finding this thread--at least now I know my experience is not totally unique.
The same thing happened to my wife's Galaxy Nexus, which came as a yakjuwx 4.0.2. After applying the OTA update to 4.0.4, the phone will invariably reboot by itself within 30-40s in standby. The Samsung service centre (in Singapore) even took the trouble to change the motherboard (so they claimed) but that didn't resolve issue. But since they only have the 4.0.2 ROM on hand and will always flash the device back to that, and since the phone does not exhibit the problem in 4.0.2, the problem is solved as far as they are concerned. After discussing a bit with one of their engineers, he even advised me to hold off updating to 4.0.4.
The amazing thing is that the same pattern of problems persist even if I flash the phone to the Google factory images (yakju). The phone will be fine in yakju 4.0.2, but not after the OTA update to either 4.0.4, or 4.1.1. This suggests that there is something hardware related involved, but there's no way for me to prove it.
Currently, the phone is running Google factory image yakju 4.0.2 without problems. To stop the OTA notification from shoping, I've rooted the device, used Root Explorer to (1) delete the OTA update file in /cache and (2) renamed system/etc/security/otacerts.zip to otacerts.zip.bak. After one restart, I said "yes" to the update notification, which then immediate shows that the phone is up to date, and it has not been bothering since. Since my wife is not big on the 'latest and biggest' upgrades, this seems an acceptable solution for her.
This obviously happens only to some Galaxy Nexus. My own device, an identical yakjuwx 4.0.2 model, updated OTA to 4.0.4 without any issues. It was subsequently upgraded unofficially to yajku 4.1.1 and ran well for a week. But something else happened--it heats up while simply refusing to charge--and it's also returned for servicing. Sad to say this but I'm slightly regretting going with the two Nexus...
(*Incidentally, for all their inability to solve the problem at a more fundamental level, and more strangely, their lack of the facility to install the yakjuwx 4.0.4 update themselves, the Samsung service centre people in Singapore have been very friendly and helpful. They were also very lenient with the warranty--I didn't have a proper receipt as the phone was purchased second hand but they accepted it on the basis of the serial number. Furthermore, they didn't make any comment about the fact that the bootloader was unlocked. It seems their policy to simply flash any phone given to them for servicing back to factory yakjuwx 4.0.2 no questions asked, before proceeding with further tests. I was warned, of course, that any phones left with them will be wiped.)
I had no issues with 4.0.2, it was only 4.0.4 that seemed to be a problem for my device.
Uptime now 275 hours on 4.1.1 :thumbup:
Sent from my Galaxy Nexus using xda premium
Related
Hi XDA,
I'm new to Android (first Android phone), and have never done any unlocking/rooting/etc. I've been working in iOS-land for 4 years, but wanted to try something new and refreshing.
I'm trying to figure out why my TELUS GSM Galaxy Nexus is stuck on 4.0.1? If my searching/reading is correct, it sounds as though the factory build they put on isn't eligible (yet) for the update, so you have to put on a different ROM entirely? (the yaku...something).
I thought the updates were pushed out by Google, not the carrier (e.g. TELUS/Rogers/Fido/etc). Why is everyone else running 4.0.2 or later (I know CDMA is even farther ahead) and I'm stuck at 4.0.1? And if CDMA is all the way up at 4.0.4, why isn't GSM? Wouldn't the people implementing bug fixes, etc, be updating for both platforms simultaneously?
I was oping factory updates would come quicker? I never wrecked any of my iOS devices (came pretty close, but eventually mastered DFU mode, pwning, and worst case scenario, rolling back to stock iOS 4 or 5). If I brick my Nexus though, I'm going to be in a world of hurt.
jasphair said:
Hi XDA,
I'm new to Android (first Android phone), and have never done any unlocking/rooting/etc. I've been working in iOS-land for 4 years, but wanted to try something new and refreshing.
I'm trying to figure out why my TELUS GSM Galaxy Nexus is stuck on 4.0.1? If my searching/reading is correct, it sounds as though the factory build they put on isn't eligible (yet) for the update, so you have to put on a different ROM entirely? (the yaku...something).
I thought the updates were pushed out by Google, not the carrier (e.g. TELUS/Rogers/Fido/etc). Why is everyone else running 4.0.2 or later (I know CDMA is even farther ahead) and I'm stuck at 4.0.1? And if CDMA is all the way up at 4.0.4, why isn't GSM? Wouldn't the people implementing bug fixes, etc, be updating for both platforms simultaneously?
I was oping factory updates would come quicker? I never wrecked any of my iOS devices (came pretty close, but eventually mastered DFU mode, pwning, and worst case scenario, rolling back to stock iOS 4 or 5). If I brick my Nexus though, I'm going to be in a world of hurt.
Click to expand...
Click to collapse
Id like to know this too. Im on Rogers and have the Rogers version of the GNEX and it too came with v4.0.1
I have since rooted, etc and flashed a custom 4.0.3 ROM (see signature for info) but I seem to be having some network issues (bug in 4.0.3 custom ROMS) which may FORCE me to go back to stock and if I do then Id definitely like to know WHY we have not received any Official updates to our devices as of yet...
Your updates are coming from google not your carriers. However Samsung is in charge of ensuring the update works in certain regions hence the delay.
Sent from my Galaxy Nexus using XDA App
yiannisthegreek said:
Id like to know this too. Im on Rogers and have the Rogers version of the GNEX and it too came with v4.0.1
I have since rooted, etc and flashed a custom 4.0.3 ROM (see signature for info) but I seem to be having some network issues (bug in 4.0.3 custom ROMS) which may FORCE me to go back to stock and if I do then Id definitely like to know WHY we have not received any Official updates to our devices as of yet...
Click to expand...
Click to collapse
Google hates Canada.
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
ray2jerry said:
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the info but as I mentioned, I am already running a Custom 4.0.3 ROM but I seem to be having signal drop issues with it so I may have to flash something else to fix that as I have read that these signal drop issues are 4.0.3 AOSP ROM related...
ray2jerry said:
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That can't be right. The only OTA update that went out for yakjuux was the volume fix update. I've never heard of anyone getting 4.0.2 that had yakjuux. The first batch of phones that came out in December received that volume update but it stayed 4.0.1. Any phones bought recently already came with the volume update applied.
So I just bought the GSM version of the Galaxy Nexus. It is yakju and I am using it with AT&T. No matter how many times I've tried I cannot get the phone to do an OTA update to at least 4.0.2, let alone 4.0.4. So I have a couple questions, keeping in mind that I am not particularly interested in rooting and would rather just do an OTA update.
1. Will the 4.0.2 update eventually come through if I wait? I don't mind waiting, but I don't want to wait indefinitely without making any progress.
2. If I do want to or need to do a manual update, can I go straight from 4.0.1 to 4.0.4?
Like I said, I would prefer to wait for the OTA update as I'm having no issues with 4.0.1 right now.
On a completely unrelated note, I have 14 days to return this phone. If you were me, would you return it and wait for the One X. I like the idea of having a raw android Google phone, but the One X seems attractive.
I think you should get an iphone.
iphone. helping computer illiteracy become popular since 2007.
I received my Nexus about a week ago. Within 5 minutes of turning it on I received the 4.02 OTA update. 10 minutes later I was rooted and running CM9 so I can't say if I would have received the 4.04 OTA update.
Sent from my Galaxy Nexus using xda premium
get stock images and flash to 4.0.4.
search the forums on how to do that.
rsawlani said:
Like I said, I would prefer to wait for the OTA update as I'm having no issues with 4.0.1 right now.
Click to expand...
Click to collapse
Then just wait for the OTAs.
On a completely unrelated note, I have 14 days to return this phone. If you were me, would you return it and wait for the One X. I like the idea of having a raw android Google phone, but the One X seems attractive.
Click to expand...
Click to collapse
There are already lots of spammy nerd bashing threads on this topic. No one can make this decision for you.
You have a few options....
1. Download Factory images for 4.0.4 from Google and use Galaxy Nexus Toolkit to flash (you will lose all your data and pictures, videos, music)
2. Root your phone (you'll still lose your data because you have to unlock your bootloader)
3. Wait for the 4.0.2 update than the 4.0.4 update
Your choice
When you get the HTC One X you gonna be saying how much you wish you had AOSP
Sent from my GT-P7510 using xda premium
YoungAceAtlanta said:
You have a few options....
1. Download Factory images for 4.0.4 from Google and use Galaxy Nexus Toolkit to flash (you will lose all your data and pictures, videos, music)
2. Root your phone (you'll still lose your data because you have to unlock your bootloader)
3. Wait for the 4.0.2 update than the 4.0.4 update
Your choice
When you get the HTC One X you gonna be saying how much you wish you had AOSP
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Or when Android 5.0, "when will One X be getting Android 5.0?!"
Same Here
I guess were both on the same boat Except i am on Tmobile. As soon as i unboxed and setup my Gnex this past friday i was expecting an OTA update to 4.0.4. But appearantly that wasn't the case as i am still stuck on 4.0.1 two days later. I am really hoping i get that OTA soon...there is no way i am rooting ever again. My last phone which was a Samsung Vibrant had a custom ICS rom...everything was well until i was greeted by the deadly "Encryption Unsuccessful" screen not knowing what to do i hit reset phone. 1 min later my phones only use was as a door stop.
I know this may sound kind of silly but maybe we haven't received our updates because its the weekend . Im waiting till monday to see if i get the OTA update. Hopefully it arrives soon.
Merio90 said:
I guess were both on the same boat Except i am on Tmobile. As soon as i unboxed and setup my Gnex this past friday i was expecting an OTA update to 4.0.4. But appearantly that wasn't the case as i am still stuck on 4.0.1 two days later. I am really hoping i get that OTA soon...there is no way i am rooting ever again. My last phone which was a Samsung Vibrant had a custom ICS rom...everything was well until i was greeted by the deadly "Encryption Unsuccessful" screen not knowing what to do i hit reset phone. 1 min later my phones only use was as a door stop.
I know this may sound kind of silly but maybe we haven't received our updates because its the weekend . Im waiting till monday to see if i get the OTA update. Hopefully it arrives soon.
Click to expand...
Click to collapse
Most OTAs roll out in groups. Well at least from the last time I did a OTA .. I guess thats how they still work. Only so many users get them at a time. Not everyone who has a gnex get it at once
Sent from my Galaxy Nexus using xda premium
YoungAceAtlanta said:
Most OTAs roll out in groups. Well at least from the last time I did a OTA .. I guess thats how they still work. Only so many users get them at a time. Not everyone who has a gnex get it at once
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Now that I see other people having this problem, I think OTA updates for 100% stock Android 4.0.1 Samsung i9250 Galaxy Nexus are just not happening at all for now... (verbiage/garbiage deleted
As for my Nexus One(s)... (I'll just say I never saw this happen)
EDIT:
At about 8pm MDT (GMT-06:00) in the US, my i9250 finally updated from 4.0.2 to 4.0.4. I consider this an important validation of the integrity of my device. Earlier today I flashed 4.0.2 but still had to wait.
So clearly there was a period of days (March 30 to April 2 at least) that OTA updates where not happening for the i9250. This was alarming because I've rolled my i9250 back to 100% stock Android 4.0.1 several times after playing with different ROMs. Each time it quickly updated to 4.0.2. This time it took a few days. For a while I was worried my phone had a problem.
I just rolled back to a stock ROM 4 days ago.
But did only get 1 OTA update immediately after first boot. The one from ITL41D to ITL41F (4.0.1).
No OTA to 4.0.2 or even 4.0.4 yet. (All imgs are stock ITL41F with locked bootloader of course)
Hey everybody. So I've had this device since December and when the 4.0.4 update was released for VZW users, I was not able to update. Upon further research, I found out that there was a mistake in the factory and the recovery image was not flashed, meaning I could not update software or perform factory resets. I brought it into Verizon and got a replacement, but I got a refurb with terrible signal issues. I went back to Verizon and they told me I could get a new phone. I am now eligible to get a new phone for free as a replacement. I purposely kept the Gnex until now so I could swap it out for the SIII that is releasing tomorrow. I actually fixed my Gnex on my own by flashing stock images of the 4.0.4 manually. So the question is, should I revert my phone back to 4.0.2 and leave out the recovery image when flashing in order to get the SIII, or keep my Gnex which is now working perfectly fine?
jttate04 said:
Hey everybody. So I've had this device since December and when the 4.0.4 update was released for VZW users, I was not able to update. Upon further research, I found out that there was a mistake in the factory and the recovery image was not flashed, meaning I could not update software or perform factory resets. I brought it into Verizon and got a replacement, but I got a refurb with terrible signal issues. I went back to Verizon and they told me I could get a new phone. I am now eligible to get a new phone for free as a replacement. I purposely kept the Gnex until now so I could swap it out for the SIII that is releasing tomorrow. I actually fixed my Gnex on my own by flashing stock images of the 4.0.4 manually. So the question is, should I revert my phone back to 4.0.2 and leave out the recovery image when flashing in order to get the SIII, or keep my Gnex which is now working perfectly fine?
Click to expand...
Click to collapse
Keep the gnex and flash jellybean or cm9/aokp
Sent from my Galaxy Nexus using xda premium
If you want the extra RAM and locked bootloader, take it back and get the SIII.
If you want a phone with 4.1.1 today keep the Nexus, go to development section and flash jellybean already
Really wish people would grow a pair and just choose the device that they want, rather than asking a bunch of strangers that know nothing about them.
martonikaj said:
Really wish people would grow a pair and just choose the device that they want, rather than asking a bunch of strangers that know nothing about them.
Click to expand...
Click to collapse
It's perfectly valid for someone to seek the opinions of others to help them in their decision.
Do mods matter to you
If you want to be able to easily load mods to your phone keep the Galaxy Nexus. If you want a painless, but Verizon-controlled environment get the SIII. If I was in your position I'd keep the Gnex, but your priorities may be different.
It really depends on what you're going to do with your phone. If you go the GS3 route, just be aware that given the current situation with the locked bootloader, your ability to customize the phone will be compromised, until devs really find an effective way to bypass the bootloader. There is the Developer Edition of the Verizon Galaxy Nexus, but that seems to be only available through Samsung and not Verizon.
At least by sticking with the Nexus, you have access to all the available custom roms now, as well as JB and so forth.
Sent from my Nook Color using Tapatalk
CKTurbo128 said:
It really depends on what you're going to do with your phone. If you go the GS3 route, just be aware that given the current situation with the locked bootloader, your ability to customize the phone will be compromised, until devs really find an effective way to bypass the bootloader. There is the Developer Edition of the Verizon Galaxy Nexus, but that seems to be only available through Samsung and not Verizon.
At least by sticking with the Nexus, you have access to all the available custom roms now, as well as JB and so forth.
Sent from my Nook Color using Tapatalk
Click to expand...
Click to collapse
Don't forget the wonderful gift of touchwiz
Has Google released the links for JellyBean for LTE Devices yet? I'm not using a GSM
jttate04 said:
Has Google released the links for JellyBean for LTE Devices yet? I'm not using a GSM
Click to expand...
Click to collapse
No. There's no Verizon or Sprint OTAs yet. Source is out for GSM and Verizon though.
I'd get the GS3. If you find out you made the wrong choice you can sell the GS3 and re-buy a Nexus and make $.
You fixed terrible signal issues by flashing the phone? That's weird as signal issues have been reported as hardware related all over this forum.
But as its now fixed and working for you, I'd certainly keep it..There's a reason why you bought it in the first place, since its working why not keep it and save your upgrade.
For me, after having the freedom of a unlocked bootloader I'm not sure I can ever own a non-nexus device again!
I updated to jellybean on my VZW nexus and have been dropping my signal a bunch randomly. I just got a refurbished phone from verizon and I flashed it first thing so I don't know if it is a problem with the phone or the stock AOKP radios I have installed. I was wondering if anyone knew if I can use the radios from 4.0.4 on jellybean or not?
rustid said:
I updated to jellybean on my VZW nexus and have been dropping my signal a bunch randomly. I just got a refurbished phone from verizon and I flashed it first thing so I don't know if it is a problem with the phone or the stock AOKP radios I have installed. I was wondering if anyone knew if I can use the radios from 4.0.4 on jellybean or not?
Click to expand...
Click to collapse
I don't know the answer to your question, however...
Got my wife a free Galaxy Nexus from Best Buy last week (verizon)... and instantly had problems w/ the 4g. After a ridiculous period of time at Best Buy to get the phone activated (they tried multiple SIM cars) and her contacts downloaded, we finally left being assured that the 4g problems were due to the activation process, and were told to give it a day or two. I was skeptical.
So we flipped off the LTE/CDMA mode, and went just to CDMA and used 3g for a few days. Called Verizon, they refreshed the network / cleared out the lines (whatever that means), and still no 4g. Every time we'd turn on 4g mode, it would connect, then drop moments later. When it dropped, it also dropped the phone line. After a week, my wife had finally worn me down. I conceded to her that a very very very very remote possibility had occurred, and we had gotten 'a bad phone'. Dear lord, did I want her to go to Best Buy w/o me. But i got suckered (she's pregnant).
So after another 2 hours at Best Buy, a new phone, and a new SIM card... we walked out w/ the same problem as before. Apparently, there's something going on w/ Verizon's latest software version ... our only option is to use 3g for a bit. I called Verizon to try and get some free money towards my bill out of them, and the customer support rep told me my best option at this point was to return the phone and choose a different device. Talk about horrible support.
So now i've come here to pretty much try what i think you'er aiming for... maybe by going to CM9 or CM10, her phone will be able to keep a constant 4g connection... only time will tell.
rustid said:
I updated to jellybean on my VZW nexus and have been dropping my signal a bunch randomly. I just got a refurbished phone from verizon and I flashed it first thing so I don't know if it is a problem with the phone or the stock AOKP radios I have installed. I was wondering if anyone knew if I can use the radios from 4.0.4 on jellybean or not?
Click to expand...
Click to collapse
There is no such thing as "stock AOKP radios." The baseband version is independent of the ROM, so whatever baseband you had after flashing was the exact same one you had prior. The signal drops are a common issue and could be attributable to the fact that there are no JB basebands released for the i515 as of yet.
The issue is with your device and not the radio's or the OS version you are on. Nothing you do will fix it or make the issue disappear. There are good GNEX's out there that do not have the radio problems, it took me three tries to get one.
Don't believe anything else you hear about fixing what you have. It is all BS.
Occam's Razor is applicable here. When the problem is persistent on 4.1.1 and is not present after reverting to 4.0.4, it's a software issue. That's not discounting the ones put there with hardware issues, but the fact of the matter is that signal problems are to be expected for vzw users running JB. We have updated binaries, but until a new baseband drops for the i515, it's not going to play especially well with JB. Such is the price for us early adopters.
Sent from my Galaxy Nexus using Tapatalk 2
[email protected] said:
The issue is with your device and not the radio's or the OS version you are on. Nothing you do will fix it or make the issue disappear. There are good GNEX's out there that do not have the radio problems, it took me three tries to get one.
Don't believe anything else you hear about fixing what you have. It is all BS.
Click to expand...
Click to collapse
I've seen two types of issues on the gnex.
1) 4g drops out and either drops to 3g or 1x for a period of time, in which it reconnects to 3g/4g shortly after. This seems to be a once in a while type issue. This seems to be more radio related.
2) 4g drops and your phone drops signal, period, for that time and then reconnects quickly. Easiest way to tell if its doing that is to check the battery stats graph and look for red slivers in your data connection. This issue from what I've seen is more hardware and I'd suggest replacing the device within your 14 days.
Sent from my Galaxy Nexus using Tapatalk 2
The ongoing theme is it's a great phone other than noisy calls, occasional drops, data signal/connection issues, and fragile glass.
And we're partly to blame. Short life cycles and youthful koolaid drinking consumers enable phone manufacturers to continue to build with a style over function mentality.
najaboy said:
Occam's Razor is applicable here. When the problem is persistent on 4.1.1 and is not present after reverting to 4.0.4, it's a software issue. That's not discounting the ones put there with hardware issues, but the fact of the matter is that signal problems are to be expected for vzw users running JB. We have updated binaries, but until a new baseband drops for the i515, it's not going to play especially well with JB. Such is the price for us early adopters.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
My 3rd replacement says otherwise. I have been on JB for 3 weeks now with this device and have not had any issues with 4G.
If every LTE GNEX had the same issue on JB I would agree with you but that is not the case. I wouldn't believe it either until I finally received a perfectly working GNEX. Always thought it was the software but I was proven wrong.
rustid said:
I updated to jellybean on my VZW nexus and have been dropping my signal a bunch randomly. I just got a refurbished phone from verizon and I flashed it first thing so I don't know if it is a problem with the phone or the stock AOKP radios I have installed. I was wondering if anyone knew if I can use the radios from 4.0.4 on jellybean or not?
Click to expand...
Click to collapse
Go here and get the FC04/FC05 radios.
Radios are independent of the ROM, so you can install any radio you want on any ROM. FC04/FC05 are the latest basebands.
jpinsl said:
Go here and get the FC04/FC05 radios.
Radios are independent of the ROM, so you can install any radio you want on any ROM. FC04/FC05 are the latest basebands.
Click to expand...
Click to collapse
His device should already have these radios if he recently received it.
My suggestion is do not play games with radio swapping, keep excahging until you get one that works.
Also, why not restore to ICS first and see that it is your phone and not the software.
najaboy said:
Occam's Razor is applicable here. When the problem is persistent on 4.1.1 and is not present after reverting to 4.0.4, it's a software issue. That's not discounting the ones put there with hardware issues, but the fact of the matter is that signal problems are to be expected for vzw users running JB. We have updated binaries, but until a new baseband drops for the i515, it's not going to play especially well with JB. Such is the price for us early adopters.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
My old phone with the blown speaker on the same 4.1.1 rom does not have this issue. I never tried stock ICS, I flashed this phone as soon as I got it. I think it is the phone.
I have the drop issue sometimes but in my case I'm sure its not the phones fault as it doesn't happen at home (only at work)
Sent from my Galaxy Nexus using Tapatalk 2
Running jellybean now, but my 4g has always been erratic at connecting. Sometimes its fine and sometimes it switched back and forth in the same location.
Sent from my Galaxy Nexus using xda premium
I tried searching for a solution, but I was unable to find one. If such a thread exists, I apologize.
I recently got a used Sprint Galaxy Nexus. The day I got it, after factory resetting and getting stock, unrooted 4.0.4, I was prompted for an update, and of course accepted. While rebooting after the update, I got the image of the android with the red triangle/warning symbol. So after waiting for a bit, I took out the battery. Everything rebooted as normal. As I have learned in the past few days, that was the FD02 update, and upon checking my build number, I see that I am still on FC12. Earlier today I got another prompt to update, and once again it failed to reboot. I have noticed that 3g reception has been rather poor, and it is to my knowledge that that is precisely what FD02 is supposed to address.
If anyone has any solutions as to why a stock, unrooted device cannot complete an OTA update, I'm all ears.
Thank you
Flash the fc12 modems listed in the ota fix sticky thread in the sprint galaxy nexus Dev section.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks lol. I was looking only in this subforum, and didn't even notice there was one specifically for Sprint GNs. I'm dumb.