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

[Q] GNEX loosing connection after 4.2.0 or 4.2.1 - cause or coincidence?

My GNex (yakju) is losing data connection so often now since I received 4.2.0 it's not even funny. I updated to 4.2.1 and problem is still there. The only way to get connection back is to toggle airplane mode a few times or reboot.
Background: I had this problem when I purchased the phone which was on 4.0.1 originally. I eventually found out about this site and updated to 4.1.1 using mskip's GNex TOOLKIT. Miracle, no more data connection loss! I could now fully enjoy the GNex and has been functioning flawlessly for several months. When 4.1.2 came out, I updated OTA and phone was still working perfectly.
Now 4.2.0 came out, received it OTA - horror: my connection loss problems are worse than ever So I though OK I will just go back to 4.1.2, but problem remains. OK then I'll go back to 4.1.1, but problem remains! Reset factory settings, flashed phone several more times re-trying 4.1.1, 4.1.2, 4.2.0, 4.2.1... no success. Checked APN, reset APN as per provider settings (Telus in Canada) but without success.
My connection now drops all the time. I miss about 90% of my calls, notifications, etc. Google search finds several people with similar problems and indicate some GNex have hardware problems and the solution is to ask Samsung for an exchange until you get a good one but often takes 3-4-5 phone swaps before getting a good one.
I just find it is a very strange coincidence that my phone "broke" immediately after updating to 4.2.0. Anyone has any ideas how I could solve this problem (other than going to Samsung for a swap because this is a nightmare road I'd which to avoid)?

Had a similar issue lost service altogether, used mskips gnex toolkit to wipe all then download and flash stock google image, immediately fixed issue so did one click root busybox etc and regained root then flashed a custom rom, no dramas since and smooth as butter.
Hope this helps am somewhat of a noob so dont know tech stuff but toolkit did the job and fixed it, its a software bug methinks, many thanks to mskip and xda
sent via xda app from my yakju gnex 4.2.1 paranoid android 2.99 beta 6

Dan Demonic said:
Had a similar issue lost service altogether, used mskips gnex toolkit to wipe all then download and flash stock google image, immediately fixed issue so did one click root busybox etc and regained root then flashed a custom rom, no dramas since and smooth as butter.
Hope this helps am somewhat of a noob so dont know tech stuff but toolkit did the job and fixed it, its a software bug methinks, many thanks to mskip and xda
sent via xda app from my yakju gnex 4.2.1 paranoid android 2.99 beta 6
Click to expand...
Click to collapse
I already re-flashed my phone countless times with with the latest gnex toolkit trying various ROM setup such as 4.1.1, 4.1.2, 4.2.0, 4.2.1 with no success. Then I tried flashing several different recent or older radios (UGKL1, UGLC1, UGLH1, XXLF1, XXLH1) with again no success. Now pretty much anytime I wake my phone, my connection is grayed out whichever ROM (stock) or radio I tried.
I haven't tried is trying all radios on older ROMs yet and I only tried the different radios on 4.2.1. Then again I feel I shouldn't have to do all this and think its getting ridiculous, I mean the latest build should be reliable.

Home Button not Responsive JB Update

Hey guys,
Just wondering if anyone else on the Rogers Galaxy S3 is experiencing this same issue after updating to Rogers Jelly Bean 4.1 update, or loaded the rooted JB 4.1 software. I've factory reseted my phone 3 times now. Same issue. I'm on rooted JB 4.1
I've called both Rogers and Samsung, they say theyve never heard of this. Told me to Factory Reset. I've done this 3 times now
Phone has NEVER been dropped.
Weird thing that happened last night with the official update. And has never happened before. When the screen is completely off, we usually wake it up by pressing the home button. Well its happened a few times where I pressed the home button (not super hard) but screen doesnt turn on. Press it again a few secs later same amount of force, and screen turns on. This never happened on ICS stock Rogers.
I'm not sure if its my phone or something with JB.. I'll try to take battery out and place it back in and see if it does this same thing again
Another member on a different forum has replied that this was an issue on the Cyanogenmod10 ROM as it was ported from the Jelly Bean 4.1 ROM:
FWIW the home button not consistently waking up the phone is a prevalent issue on CyanogenMod 10 (which is based on Android 4.1). I had the issue on CM10 but I haven't experienced it since switching to AOKP.I've called both Rogers and Samsung, they say theyve never heard of this. Told me to Factory Reset. I've done this 3 times now
Click to expand...
Click to collapse

Any CM10 issues are not related to TouchWiz. They are two different worlds. CM10/AOKP are based on AOSP which is vanilla Android, there is no Samsung code in there at all.
Have you loaded ICS back on to see if the issue still exists? Are you able to warranty your device in case it might be a hardware issue?

There is something called "Power" button... it was made for unlocking the screen beside powering function....
Download Rogers stock ROM and flash, it should fix.

Tony_YYZ said:
Any CM10 issues are not related to TouchWiz. They are two different worlds. CM10/AOKP are based on AOSP which is vanilla Android, there is no Samsung code in there at all.
Have you loaded ICS back on to see if the issue still exists? Are you able to warranty your device in case it might be a hardware issue?
Click to expand...
Click to collapse
The thing is I've never dropped this phone since getting it in Nov. So I dont think its hardware issue. Then again I'm not a phone tech. Is it possible to load back on Stock Rogers ICS through Odin again? Same process as rooting? I have stock recovery and not clockwordmod
Thanks for the input
yulet said:
There is something called "Power" button... it was made for unlocking the screen beside powering function....
Download Rogers stock ROM and flash, it should fix.
Click to expand...
Click to collapse
Yes I realize I can wake the phone up from pressing power button. May'be I'll just do this from now on. I'm guessing most ppl wake their phones up by pressing power button as well?
I'll load back on the Rogers stock ROM ICS and see if the issue is still there.
Thanks for the input

If you bump up the min cpu speed from 386 to 486, either through the ROM settings or an app like SetCPU, this seems to resolve the problem.

BenW23 said:
The thing is I've never dropped this phone since getting it in Nov. So I dont think its hardware issue. Then again I'm not a phone tech. Is it possible to load back on Stock Rogers ICS through Odin again? Same process as rooting? I have stock recovery and not clockwordmod
Thanks for the input
Yes I realize I can wake the phone up from pressing power button. May'be I'll just do this from now on. I'm guessing most ppl wake their phones up by pressing power button as well?
I'll load back on the Rogers stock ROM ICS and see if the issue is still there.
Thanks for the input
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1739426
Follow those instructions on how to flash a stock ROM. You can find the ICS factory software at www.sammobile.com Or use the rooted versions provided by MrRobinson
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
goodtimes50 said:
If you bump up the min cpu speed from 386 to 486, either through the ROM settings or an app like SetCPU, this seems to resolve the problem.
Click to expand...
Click to collapse
OP is running TouchWiz and therefore cannot alter these settings. Those apply to the CM10/AOKP home button issue. Although what OP is describing is similar it is not the same....unless OP has CM10 or AOKP installed prior to installing the official JB update and didn't mention it in his first post.

Tony_YYZ said:
Go here: http://forum.xda-developers.com/showthread.php?t=1739426
Follow those instructions on how to flash a stock ROM. You can find the ICS factory software at www.sammobile.com Or use the rooted versions provided by MrRobinson
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
OP is running TouchWiz and therefore cannot alter these settings. Those apply to the CM10/AOKP home button issue. Although what OP is describing is similar it is not the same....unless OP has CM10 or AOKP installed prior to installing the official JB update and didn't mention it in his first post.
Click to expand...
Click to collapse
I was running stock Rogers ICS 4.0.4 then updated to JB 4.1 via Kies. Then rooted with a stock Rogers JB 4.1 ROM
Never had any custom ROM's. I will load up the stock Rogers ICS and see if the problem still persist. Will report back
Thanks again for the help guys :good:

This happens on my AT&T GS3 since the Jelly bean update, but I think it is due to the root. It's no big issue, I never use the home button anyways to unlock the screen.

Bump
I took the time yesterday to load back on the stock Rogers ICS 4.0.4 ROM and played with the home button for several hrs (4hrs) at random times pressing the home button to wakeup the phone. Everytime I pressed the home button it would wake the phone up without issues. I can conclude that ICS had no issues with waking the phone up via home button.
I then reloaded back my JB 4.1 w/root and the home button glitch reappeared again.. Its a minor inconvenience. But I now use my power button to wake the phone up anyways.

goodtimes50 said:
If you bump up the min cpu speed from 386 to 486, either through the ROM settings or an app like SetCPU, this seems to resolve the problem.
Click to expand...
Click to collapse
REALLLLLLY? thats interesting will be testing this now...
JWC59382 said:
This happens on my AT&T GS3 since the Jelly bean update, but I think it is due to the root. It's no big issue, I never use the home button anyways to unlock the screen.
Click to expand...
Click to collapse
This has definitely been happening to me on my AT&T SG3 too. Will be testing the above suggestion with my MIUI.US ROM.

[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).

[Q] Tablet turning off when not being used after upgrading to Kitkat 4.4.2

Upgraded my Note 10.1 2014 edition to KitKat 4.4.2 with the download from Sammobile, first with the Colombia then with the Cellular South firmware, all works fine but the tablet turns itself off after a short time of inactivity. The only way to get the tablet to start back up is to press the power button as if it is a normal power up. Is anyone else having this issue? I've checked all of the settings and find no way of solving this. Please advise, thanks.

Morqua said:
Upgraded my Note 10.1 2014 edition to KitKat 4.4.2 with the download from Sammobile, first with the Colombia then with the Cellular South firmware, all works fine but the tablet turns itself off after a short time of inactivity. The only way to get the tablet to start back up is to press the power button as if it is a normal power up. Is anyone else having this issue? I've checked all of the settings and find no way of solving this. Please advise, thanks.
Click to expand...
Click to collapse
Are you using any custom kernels ? if not , then a factory reset would be the best scenario for your problem.

lsherif said:
Are you using any custom kernels ? if not , then a factory reset would be the best scenario for your problem.
Click to expand...
Click to collapse
Not using any custom kernels and have tried to reset to factory settings on both Colombia and Cellular South firmware, nothing seems to work, and the tablets turns itself off if it is not being used. I'm sure this issue was caused by the 4.4.2 upgrade as nothing like this happened before the upgrade. Really don't know what else to do.

Same thing happened to me after I rooted on 4.3 & 4.4.2. I would always have to power it back on. When I unrooted, the problem went away.
Sent from my SM-P600 using xda app-developers app

Thanks for the input Russ, but mine isn't rooted. I guess I will have to hope for a firmware upgrade to come out soon, and see if that will help to fix the issue.

strange, I do exactly the same and have no issue.
USA version flashed, no wipe and all seems to be fine.
Did you try to wipe your tab to see if issue still exist ?

lightman33 said:
strange, I do exactly the same and have no issue.
USA version flashed, no wipe and all seems to be fine.
Did you try to wipe your tab to see if issue still exist ?
Click to expand...
Click to collapse
No wipe, just factory reset, unless they are the same :angel:.

Well this is probably what you don't want to hear but I had a similar problem, my stock 4.3 unit rebooted itself in the middle of a game (of "The Room 2" if that's important), and from that moment on started to do the same thing, I updated to the Colombian 4.4.2 to see if that would fix (including a wipe (not just a factory reset) but that didn't fix it at all, in the end I had to replace it after a short row with the gimp at PC world. Currently running the Cellular South 4.4.2 without any issues so far (bar the missing Volume/Brighness bar I mentioned in another thread).
It had all the hallmarks of a memory fault. Good luck, I hope you can fix it and that it's not hardware.

44566455 fitness
flathunt said:
Well this is probably what you don't want to hear but I had a similar problem, my stock 4.3 unit rebooted itself in the middle of a game (of "The Room 2" if that's important), and from that moment on started to do the same thing, I updated to the Colombian 4.4.2 to see if that would fix (including a wipe (not just a factory reset) but that didn't fix it at all, in the end I had to replace it after a short row with the gimp at PC world. Currently running the Cellular South 4.4.2 without any issues so far (bar the missing Volume/Brighness bar I mentioned in another thread).
It had all the hallmarks of a memory fault. Good luck, I hope you can fix it and that it's not hardware.
Click to expand...
Click to collapse
Yes, this is just weird, as this issue started after 4.4.2. What is weirder is the fact that I tried to root it by following this guide http://forum.xda-developers.com/showthread.php?t=2490805 and after multiple tries, "Rootchecker" still says that my device isn't rooted.