Develop Bugs

[Q] GSM Nexus says "Android is Upgrading" everytime I reset my Phone

So I have an unlocked GSM Galaxy. I'm still running 4.01
Every time I restart my phone, I get a message saying "Android is Upgrading" but it never upgrades to 4.02 (or .03 or whatever it should be upgrading to). Is anyone else having this issue?
I have NOT rooted yet.
When I go to check for updates it says my phone is up to date.
Any ideas?
Thanks.

pretty sure this is normal. everytime i flash something it does it to me, but every reboot after that it's fine.

PittsburghG1 said:
So I have an unlocked GSM Galaxy. I'm still running 4.01
Every time I restart my phone, I get a message saying "Android is Upgrading" but it never upgrades to 4.02 (or .03 or whatever it should be upgrading to). Is anyone else having this issue?
I have NOT rooted yet.
When I go to check for updates it says my phone is up to date.
Any ideas?
Thanks.
Click to expand...
Click to collapse
have you done any mods?
usually you get the android is upgrading when you install a new app or wipe the dalvik cache. the android is upgrading is the apps rebuilding in cache.
its quite annoying and you shouldn't have it on every boot (just the first or after a mod)

I get the same thing on 4.0.1..I'm pretty sure its normal. At least for this build
Sent from my Galaxy Nexus using XDA App

I think what it might be doing is wiping cache.
Sent from my Galaxy Nexus using XDA App

I get it too. Figured it was normal

Meaple said:
I get it too. Figured it was normal
Click to expand...
Click to collapse
hmm. all you guys on 4.0.1? thats annoying. worth the trouble to get to 4.0.2 asap
I think i was on .1 for about a day so I didn't notice it...boot time without it is superfast

ogdobber said:
hmm. all you guys on 4.0.1? thats annoying. worth the trouble to get to 4.0.2 asap
I think i was on .1 for about a day so I didn't notice it...boot time without it is superfast
Click to expand...
Click to collapse
It really only takes a sec anyway.
Sent from my Galaxy Nexus using XDA App

Mine does this to and it's kind of annoying

Mine does it every time I turn the phone on and off. Still on 4.0.1 ITL41F build too on AT&T in the US. Lasts for 2 or 3 seconds and then the phone boots up. I thought this was normal behaviour of Android trying to search for updates. Is this not happening to everyone?
Sent from my Galaxy Nexus using XDA App

OK, my friend's Verizon Nexus doesn't do it for some reason. Also, I get the notification to upgrade to 4.0.2, but it never upgrades...even if I accept the update. I thought the "UPgrading Android" and this issue were connected.
Is anyone else getting the 4.0.2 notification then the update isn't applying?
Also, I have not rooted or applied and mods to the phone. I may try a factory reset and see what happens, obviously I don't want to do that, but I'll try.
Oh and it happens every single time I boot the phone.
thanks for all the responses!

I get this, 4.0.1 UK model here.
I am sure though after a few restarts of nothing major changing then it stopped?

I used to get this on 4.0.1, but since I force upgraded to 4.0.2 I havent seen it. I downloaded to official 4.0.2 from here and applied it through CWM.

has anyone who is having this problem received the 4.0.2 upgrade notification then been unable to upgrade?
That's the boat I'm in now. It won't upgrade. I'm thinking about doing a factory reset.

PittsburghG1 said:
has anyone who is having this problem received the 4.0.2 upgrade notification then been unable to upgrade?
That's the boat I'm in now. It won't upgrade. I'm thinking about doing a factory reset.
Click to expand...
Click to collapse
Most people are sure that the 4.0.2 update got pulled as there were too many bugs with it. I wouldn't worry about it.

Just to clarify...this has happened to me about 4 times...
1) I'm notified of the update.
2) I click update now
3) I get the android guy with the lightening in his belly showing that I'm updating
4) phone restarts
5) I get the Upgrading Android and Upgrading Applications messages
6) Phone completes booting
7) When I go to about Phone Android version is still 4.0.1
Then steps 4,5,6 and 7 always repeat any time I restart my phone ever since I got my update notification about 2 weeks ago.
So, it seems as its trying to upgrade to 4.0.2 everytime I restart but it can't.
Whether they pulled the update or not, my phone was being pushed the update but was unable to update. So basically, I'm thinking will I ever be able to update or should I just wipe now as there is clearly some problem?

I get this too, on the 4.0.1 build. Only takes a few seconds tho, nothing too annoying, I thought it is normal. But thinking about it, my Desire S with a ICS custom rom only did this after an upgrade or a modification...
But I haven't got any 4.0.2 update notification yet. Received my Nex on the 28th of December.

I just ended up rooting, upgrading to 4.0.3 and its never happened again. Thanks everyone though for the feedback.

I'm on 4.0.2. Had the phone a week, it updated to 4.0.2 the first time I turned it on, then again after I unlocked the bootloader and nothing else.
It's a UK vodafone.
Sent from my Galaxy Nexus using XDA App

I have an International GNex running on T-Mobile US: I've had the same message "Android is upgrading" on all reboots when I was on 4.0.1. Since the 4.0.2 update (received OTA on January 11), the message never appeared again.
Hope this helps

Camcorder crash

Camcorder crash. Every time I try to record the camera app crashes..
I've tried a lot of roms. Aokp, cm9,bugless beasts and more
Can someone please help me?
Sent from my Galaxy Nexus using xda premium

What build and rom are you using .. ask them for a fix ...

Hi there,
i have the same problem:
Everytime i try to start video-mode, the app crashes.
When i open and close the app a few times, the cam crashes, too.
Switching from back to front cam sometimes fails, the back cam is active again (after some freeze-time).
Everything worked fine with 4.0.3 stock (open bootloader,root and cwm with GNToolKit).
The problem occurred with the update to 4.0.4. stock (IMM76D & IMM76I)
(I had to do a full wipe, cause i encrypted the phone and cwm could not load the updatefile from encrypted sdcard).
So what i've tried till now:
- clear app cache and data
- extracted camera .apk and .odex from stock 4.0.3 and moved it to /system/app but that didn't work
- Tried other cam-apps (crash)
- installed open bootloader and rooted again (GNToolKit)
- removed flashlight app
- wipe cache /dalvik cache
I don't know, what i should try next, so please help me
Thanks so far...
P.S. Since 4.0.4. all taken photos have a yellow spot. Maybe i should go back to 4.0.3.....
Galaxy Nexus with ICS 4.0.4 IMM76I

Update:
Wiped all and then installed 4.0.2 stock. Everything worked fine with the cam.
Updated OTA to 4.0.4 and now it's the same again... cam crashes if i want to take a video.

Update:
What helped? I got a new one, now everything works fine.

I did go back to stock then it began to work, now it works with any rom again
Sent from my Galaxy Nexus using xda premium

I flashed the newest update. 4.0.4 from google
Sent from my Galaxy Nexus using xda premium

i tried all variants.
Bit strange, that cam worked with 4.0.2 but not with 4.0.4.
Maybe they changed cam-api or something.
With my new gNex, cam works fine

The problem I had wasn't that the camera/video didn't work but that it couldn't save to SD . It had something to do with the permissions and the videocam crashed when I switched . The camera couldt save pictures
P.S I locked my bootloader and then opened it when I did the factory restore
Try to go back to factory a couple of times
Do u have the thumbnail in camera app?
Mine was missing..
I played a lot with the tablet mod, maybe its have something to do with it or maybe because I flashed a lot of roms. I have never seen this before.. it was kind of weird
Sent from my Galaxy Nexus using xda premium

I flashed stock rom, and i think it overwrote all permissions set before.
I locked bootloader, unrooted phone, unlocked it again, then locked it again.. several times. Nothing changed.
My new gNex came with an open bootloader, i was wondering...
The bootloader is still opened and i am root again
I think i had a hardware problem. with 4.0.4. all images i took, had a yellow spot in it. I had thumbnails, too.

maybe you were just unlucky and got a gnex with errors. Was just glad I did't have a hardware failure. I went from 4.0.2 stock ROM to a 4.0.3 costume rom. It then worked fine! when I later upgraded to 4.0.4 costume rom it went wrong . isn't the bootloader always locked? by default?
Sent from my Galaxy Nexus using xda premium

Yes, bootloader is locked by default. I don't know what they did before with this gNex.
Maybe it's not a new gNex, but one, who came back from a user, who didn't want it.
The main point is, it works

[Q] Galaxy Nexus 4.1.2 update erorr

Hi,
I own Gnex which shipped with yakjuxw firmware, but after following a guide here on xda I unlocked the bootloader and flashed stock (yakju) Android 4.0.4 (the newest version for which Google provided factory images at that time). I soon received the 4.1.1 ota update and everything went smoothly.
Today I was charging my phone while it was off, but needed to start it to search something. It was charged at 43% when i booted, and after a few seconds I received the 4.1.2 update notification. I accepted and there was a countdown to restart and then the screen went dark. It was still plugged in and I let it stay like that for a couple of minutes. Still nothing happened so I unplugged it and tried to manually restart it. I panicked for a few minutes as nothing seemed to work. I finally pulled out the battery, after which I was able to start it. It's still showing 4.1.1 and the update notification disappeared.
Should I reset Google frameworks or should I let it be for a couple of days?
Thanks,
Horatiuf4

You should be fine to continue using it like normal, if you're particularly worried just flash the factory firmware for your particular galaxy from https://developers.google.com/android/nexus/images like normal.

Try clear data google service framework and force stop it then check system update. It will show you update msg definetly. If not try again.No need to wait for some days.
Sent from my Galaxy Nexus using xda premium

Solved
Hi,
I cleared the services framework data and the notification reappeared, and the update went without a hitch.
Thanks for the responses,
Horatiuf4
P.S. Let's hope that on the 30th will be force closing our Services Framework to get the 4.2 update.

Gn frezzes after 4.2 upgrade.

Hello to all
The day before yesterday I flashed on my YAKJU GN the 4.1.2 TAKJU factory image and then the TAKJU 4.2. I am rooted with SUPERSU, I have CWM touch and i use an app to disable lock-screen widgets, other than I am stock.
Until yesterday morning everything was running normally. Yesterday night and today my phone freezes when locked, the only way to fix it is to pull the battery.
Has anyone faced the same problem?
Thanks

Haven't had this problem myself, but it sounds like the kind of issues you get with a dirty flash. My best guess would be to try a complete wipe and a fresh install. You may want to wait to see if another member has a different take on it though. Did you restore anything with Titanium Backup?
Sent from my Galaxy Nexus using xda premium

Nope...apps installed from google servers and i manually fixed the settings.
Thnks

[Q] What is wrong with my Gnex?

Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?

JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.

Are you sure it's the phone and not an app?

chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.

Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4

chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.

why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct

Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.

I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!

well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?

lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).