hi all,
every time i boot up my phone i get the "android is upgrading" message...
i already searched the forum for a solution but non worked...
- re installed titanium backup - didn't work
- wiped dalvik and cache and fixed permission - didnt work
- some people suggested deleting titanium's odex file - i cant seem to find it in /data/app (the one which is on root level)
- even full wipe wont help, it'll work fine on 1st boot but after the phone is setup i'll get the message again
i could really use some help >.<
gerberman said:
hi all,
every time i boot up my phone i get the "android is upgrading" message...
i already searched the forum for a solution but non worked...
- re installed titanium backup - didn't work
- wiped dalvik and cache and fixed permission - didnt work
- some people suggested deleting titanium's odex file - i cant seem to find it in /data/app (the one which is on root level)
- even full wipe wont help, it'll work fine on 1st boot but after the phone is setup i'll get the message again
i could really use some help >.<
Click to expand...
Click to collapse
its rebuilding your dalvik at every boot. did you flash any mod? it could also be your rom/kernel if it has a dalvik wipe script included. some devs like to trick you into believing that their mod/rom/kernel is the fastest, so they delete you dalvik on every boot. this makes it appear, yes only appear, like their stuff is extra fast. but in reality, its just a clean dalvik. also, check your init.d folder such scripts.
simms22 said:
its rebuilding your dalvik at every boot. did you flash any mod? it could also be your rom/kernel if it has a dalvik wipe script included. some devs like to trick you into believing that their mod/rom/kernel is the fastest, so they delete you dalvik on every boot. this makes it appear, yes only appear, like their stuff is extra fast. but in reality, its just a clean dalvik.
Click to expand...
Click to collapse
no it's not the rom... i'm using paranoidandroid 2.54 and i already asked in the thread... noone's experiencing it
gerberman said:
no it's not the rom... i'm using paranoidandroid 2.54 and i already asked in the thread... noone's experiencing it
Click to expand...
Click to collapse
then youre either using a custom kernel that includes such a script or youre using a mod that does it. are you using the supercharger script? if so, id get rid of it.
simms22 said:
then youre either using a custom kernel that includes such a script or youre using a mod that does it. are you using the supercharger script? if so, id get rid of it.
Click to expand...
Click to collapse
i'm using franco kernel... and paranoid android... no mods...
and as i was saying, even after a full wipe it still happens...
gerberman said:
and as i was saying, even after a full wipe it still happens...
Click to expand...
Click to collapse
it should happen after flashing a new rom, or when you clear your dalvik. check if there is a init.d folder with such a script. a wipe doesnt get rid of the init.d folder, just user data.
simms22 said:
it should happen after flashing a new rom, or when you clear your dalvik. check if there is a init.d folder with such a script. a wipe doesnt get rid of the init.d folder, just user data.
Click to expand...
Click to collapse
es file explorer cant find any init.d folder...
i do however have several init.'something' files in my root directory
gerberman said:
es file explorer cant find any init.d folder...
i do however have several init.'something' files in my root directory
Click to expand...
Click to collapse
look in either /system/etc/init.d or in /etc/init.d
simms22 said:
look in either /system/etc/init.d or in /etc/init.d
Click to expand...
Click to collapse
ok i got 2 files in both of them -
00banner and 90userinit
should i get rid of them?
gerberman said:
ok i got 2 files in both of them -
00banner and 90userinit
should i get rid of them?
Click to expand...
Click to collapse
sure. then reboot. if it still happens then we will look for the file someplace else.
simms22 said:
sure. then reboot. if it still happens then we will look for the file someplace else.
Click to expand...
Click to collapse
no =/ still rebuilding the dalvik cache...
gerberman said:
no =/ still rebuilding the dalvik cache...
Click to expand...
Click to collapse
you are using a 4.1.x rom and kernel? i just talked to Francisco Franco, he said his older kernels used to wipe dalvik upon boot.
I have similar problem. I wiped dalvik, and now it gives me Starting apps message every time it's loading. I know it's normal for apps to start lol, but I never had constant notification for it :/
Sent from my GT-I9100 using Tapatalk 2
Hmm using Franco 283...
But when I do a full wipe the kernel is wiped as well isn't it?
Sent from my Paranoid Powered Galaxy Nexus
maybe a rom/cpu control app with a wipe dalvik option?
Again, full wiping would delete these apps...
Maybe tomorrow I'll try installing an older version of the Rom... I hope it'll work cause this is starting to get frustrating
Sent from my Paranoid Powered Galaxy Nexus
gerberman said:
Hmm using Franco 283...
But when I do a full wipe the kernel is wiped as well isn't it?
Sent from my Paranoid Powered Galaxy Nexus
Click to expand...
Click to collapse
no, only user data is wiped(and apps).
simms22 said:
no, only user data is wiped(and apps).
Click to expand...
Click to collapse
you think the kernel can be the problem? i see no mention of such a problem on the kernel thread
Well I guess it was a Rom issue or something...
Flashed a new version of it and now it working fine
Sent from my Paranoid Powered Galaxy Nexus
Related
I just installed a new kernel and afterwards read about clearing the dalvik cache before installing kernels. Since I never did this should I clear it now, or do I have to clear it and then install the kernel?
clear then install
Is this the same thing as "cleaning" the dalvik cache using Titanium or do you actually have to delete the entire cache folder?
jprow507 said:
Is this the same thing as "cleaning" the dalvik cache using Titanium or do you actually have to delete the entire cache folder?
Click to expand...
Click to collapse
To be on the safe side i do it both in Titanium and then when i am in Clockworkmod, I do it in the advanced section too - by the way if you do not have partition done on your sd card u will see an E: error message. You can ignore that.
khanam said:
To be on the safe side i do it both in Titanium and then when i am in Clockworkmod, I do it in the advanced section too - by the way if you do not have partition done on your sd card u will see an E: error message. You can ignore that.
Click to expand...
Click to collapse
Thanks alot .... I did it the way you suggested and am rebooting now. I appreciate the help.
For kernels, you want to delete the cache partition, kernel stuff usually isn't help in the dalvik cache. On Amon_Ra style, it's wipe cache. On CWM I think it's wipe cache partition (Don't know, have not used CWM in a while).
jprow507 said:
Is this the same thing as "cleaning" the dalvik cache using Titanium or do you actually have to delete the entire cache folder?
Click to expand...
Click to collapse
Cleaning in Ti only deletes unneeded files. Do this after you uninstall an app or two. Wiping in Recovery clears it out completely, so you'll have a longer next boot time while it's rebuilt. You only need to wipe it when changing to and from one of King's with HAVS.
Sent from my ADR6300 using XDA App
PonsAsinorem said:
Cleaning in Ti only deletes unneeded files. Do this after you uninstall an app or two. Wiping in Recovery clears it out completely, so you'll have a longer next boot time while it's rebuilt. You only need to wipe it when changing to and from one of King's with HAVS.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
So I don't need to wipe when updating Chads incredikernel?
You should always wipe caches when swapping kernels, even it its switching kernels from the same dev. It takes like no time to do so why not? I've forgotten to and usually it makes no difference. Sometimes its just forced closed's until I can restart and do it right.
Sent from my ADR6300 using XDA App
loonatik78 said:
You should always wipe caches when swapping kernels, even it its switching kernels from the same dev. It takes like no time to do so why not? I've forgotten to and usually it makes no difference. Sometimes its just forced closed's until I can restart and do it right.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
that would be very TROLOLOLOL
Hi guys I own a htc desire 526GPLUS with mediatek 6592 and the manufacturer doesn't released source codes
Now I want to port a rom made for another device with mt6592
Can I port it and can I use drivers by copying it from driver folder from my stock rom and I will use boot. Img from stock rom
Question 2
What makes different devices require different kernels?
If I get mt6592 source code from another device can I make it to work with mine
Please help
OK so I've been trying everything and I'm tired of not been able to
Get pass the booting animation
all my other ics roms work perfect
If anyone lives near Van Nuys CA pls let me know I'll pay you to put a working JB ROM
kingviper10 said:
OK so I've been trying everything and I'm tired of not been able to
Get pass the booting animation
all my other ics roms work perfect
If anyone lives near Van Nuys CA pls let me know I'll pay you to put a working JB ROM
Click to expand...
Click to collapse
You've tried literally everything? First and foremost you Wiped Data/Cache/Dalvik and then also Formatted System and Data manually before flashing? Formatting system and data is under "Mounts and Storage." I know a lot of people wouldn't get past the boot screen because they didn't do that...
anton2009 said:
You've tried literally everything? First and foremost you Wiped Data/Cache/Dalvik and then also Formatted System and Data manually before flashing? Formatting system and data is under "Mounts and Storage." I know a lot of people wouldn't get past the boot screen because they didn't do that...
Click to expand...
Click to collapse
Ok so I wipe all 3 then I should go to mounts and mount and unmount what? Then install JB v3 ones it's done what should be mounted or unmount ?then after that just reboot system?
I'm pretty sure my problem has to do with mounting and unmount ing
kingviper10 said:
Ok so I wipe all 3 then I should go to mounts and mount and unmount what? Then install JB v3 ones it's done what should be mounted or unmount ?then after that just reboot system?
I'm pretty sure my problem has to do with mounting and unmount ing
Click to expand...
Click to collapse
Don't unmount anything.. just format /system under "Mounts and Storage"
joshnichols189 said:
Don't unmount anything.. just format /system under "Mounts and Storage"
Click to expand...
Click to collapse
I only format /system or /data (if need be) before flashing a rom, never cache or dalvik, which are hash signed. A new rom, a new flash, a new /system, has different hash, which leads to cache and dalvik being rebuilt on first boot after a flash.
sent from my i9250
Okay let me simplify everything for you and you will not need to pay anyone for assistance. All you have to do is initially erase all data and factory reset, then install the new JellyBean ROM using clockworkmod recovery and after that wipe cache and dalvik cache..you can run fix permissions (i did but not sure if it matters.) If it still is stuck on the boot screen then wipe data again, reinstall JB rom, wipe cache and dalvik cache and wipe anything else you can wipe. After all that mine started working normally. If you are still stuck sent me a PM and I can assist you from Atlanta GA and for free!
bradleyyy said:
Okay let me simplify everything for you and you will not need to pay anyone for assistance. All you have to do is initially erase all data and factory reset, then install the new JellyBean ROM using clockworkmod recovery and after that wipe cache and dalvik cache..you can run fix permissions (i did but not sure if it matters.) If it still is stuck on the boot screen then wipe data again, reinstall JB rom, wipe cache and dalvik cache and wipe anything else you can wipe. After all that mine started working normally. If you are still stuck sent me a PM and I can assist you from Atlanta GA and for free!
Click to expand...
Click to collapse
OK thanks I'm going to give it a try again were due I get the fix permission?
kingviper10 said:
OK thanks I'm going to give it a try again were due I get the fix permission?
Click to expand...
Click to collapse
Its gonna be a long proccess if you don't where to "get" fix permissions... lol
Sent from my Galaxy Nexus using xda app-developers app
kingviper10 said:
OK thanks I'm going to give it a try again were due I get the fix permission?
Click to expand...
Click to collapse
IIRC it's under advanced in CWM
Sent from my Galaxy Nexus using xda premium
3rdstring said:
IIRC it's under advanced in CWM
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I guess the other member was right I'm on my s3 searching and can't seem to find it ? Can u pls get me a link sorry but im new to the forum really appreciate all the help
kingviper10 said:
I guess the other member was right I'm on my s3 searching and can't seem to find it ? Can u pls get me a link sorry but im new to the forum really appreciate all the help
Click to expand...
Click to collapse
Go into ClockworkMod Recovery, then Advanced, then Fix Permissions
I had a very hard time doing it too. The first time I did it I, when I setup the phone, it kept having every app crash, one after another. Managed to get back into CWM and try to restore my ICS and it kept giving me errors. I finally read something about a super wipe, but it didn't say it worked for the GNex, so I just did a cache wipe, and did the data wipe 4 times, and then installed JB one more time, and it finally worked. I never had to fix permissions or anything like that. Perhaps your phone just needs some extra wipes like mine.
harveydent said:
Go into ClockworkMod Recovery, then Advanced, then Fix Permissions
Click to expand...
Click to collapse
Ok so I did everything u said I'm passed the Google screen and now on the X screen crossing my fingers that this works
I have run three different ROMs, CM10. AOKP Jelly Bean Build 1, and Jelly Belly all of which the System UI stops 4 times every hour and then about 45 seconds later it starts back up. It is quite annoying.
Can someone help me in stopping such madness?!
Utopia73 said:
I have run three different ROMs, CM10. AOKP Jelly Bean Build 1, and Jelly Belly all of which the System UI stops 4 times every hour and then about 45 seconds later it starts back up. It is quite annoying.
Can someone help me in stopping such madness?!
Click to expand...
Click to collapse
factory reset and reflash rom
Sent from my i9250
bk201doesntexist said:
factory reset and reflash rom
Sent from my i9250
Click to expand...
Click to collapse
If you meant just through cwm I did that and nothing changed it still occurs.
Are you using Titanium Backup or similar and restoring system data? If so, don't.
Sent from my Galaxy Nexus using xda app-developers app
killyouridols said:
Are you using Titanium Backup or similar and restoring system data? If so, don't.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Nope. I downloaded a fresh ROM and wiped everything, then flashed.
Odd. Strange that you have the same issue with 4 different ROMS. Because of this It sounds like there is something inherently wrong with the hardware or, even more oddly, an issue with all 4 ROMs which the only thing I can think of is that you have downloaded incorrect versions for your phone (sorry to sound like I'm insulting your intelligence but that's all I can think of)
The only think linking the errors across all the roms would be something which they all share, in this case imcompatable software.
Sent from my Galaxy Nexus using xda app-developers app
killyouridols said:
Odd. Strange that you have the same issue with 4 different ROMS. Because of this It sounds like there is something inherently wrong with the hardware or, even more oddly, an issue with all 4 ROMs which the only thing I can think of is that you have downloaded incorrect versions for your phone (sorry to sound like I'm insulting your intelligence but that's all I can think of)
The only think linking the errors across all the roms would be something which they all share, in this case imcompatable software.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Haha you're not insulting me. Could a hard reset work through the toolkit help?
Have you tried super wipe?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
have you tried to reflash stock through fastboot? does it happen then? are you changing dpi or something? themes? are you checking sha256 or md5 after you push it to the device? its a long shot this one, but what version of cwm are you using?
get us logcat/dmesg or it didn't happen.
When you said you wiped totally and reflashed, did you still restore from a TiBU with system apps backed up? If so, don't. Sorry if that's not the problem. Only do user apps. ONLY.
Utopia73 said:
I have run three different ROMs, CM10. AOKP Jelly Bean Build 1, and Jelly Belly all of which the System UI stops 4 times every hour and then about 45 seconds later it starts back up. It is quite annoying.
Can someone help me in stopping such madness?!
Click to expand...
Click to collapse
try different gapps. run a fix permissions too, just in case.
liquid150 said:
When you said you wiped totally and reflashed, did you still restore from a TiBU with system apps backed up? If so, don't. Sorry if that's not the problem. Only do user apps. ONLY.
Click to expand...
Click to collapse
I don't use TiBU, I do a clean install every time
bk201doesntexist said:
have you tried to reflash stock through fastboot? does it happen then? are you changing dpi or something? themes? are you checking sha256 or md5 after you push it to the device? its a long shot this one, but what version of cwm are you using?
get us logcat/dmesg or it didn't happen.
Click to expand...
Click to collapse
I have not tried to reflash stock through fastboot. I am not changing dpi or theming at all. It's a completely clean install. I am running the newest version of cwm touch. and how do I get a logcat/dmesg?
kyokeun1234 said:
Have you tried super wipe?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
Not yet, should I?
simms22 said:
try different gapps. run a fix permissions too, just in case.
Click to expand...
Click to collapse
I have downloaded a new gapps every time. And i'll do another clean install with fix permissions too
Utopia73 said:
I have downloaded a new gapps every time. And i'll do another clean install with fix permissions too
Click to expand...
Click to collapse
try these gapps, they are what i used http://db.tt/S6raPf0f
If you're out of ideas, try super wipe. Wipe everything! After that, you can adb push the Rom and flash it. Good luck
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
kyokeun1234 said:
If you're out of ideas, try super wipe. Wipe everything! After that, you can adb push the Rom and flash it. Good luck
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
Ive never done a super wipe. What does it do, like what all does it wipe. I assume it's a script
Utopia73 said:
Ive never done a super wipe. What does it do, like what all does it wipe. I assume it's a script
Click to expand...
Click to collapse
It's basically a .zip file that when you flash like other ROM or kernel, just erases everything. Simple as that. It'll erase current ROM, current kernel, files in /sdcard/, cache, dalvik, hack, all the files in the phone. It'll just leave you with a new playground for you to play on.
It might be a "overkill" for this kinda problem, but since nothing helped, I say try this.
kyokeun1234 said:
It's basically a .zip file that when you flash like other ROM or kernel, just erases everything. Simple as that. It'll erase current ROM, current kernel, files in /sdcard/, cache, dalvik, hack, all the files in the phone. It'll just leave you with a new playground for you to play on.
It might be a "overkill" for this kinda problem, but since nothing helped, I say try this.
Click to expand...
Click to collapse
wait if it wipes sdcard how am i supposed to get the new rom flashed?
Utopia73 said:
wait if it wipes sdcard how am i supposed to get the new rom flashed?
Click to expand...
Click to collapse
Use adb push.
1. Download ROM of your choice
2. Place it in the same directory as adb.exe
3. Boot your (SuperWiped) phone into recovery mode (Whether it's TWRP or CWM)
4. Open up the cmd in the directory where adb.exe is located
5. "adb push NAME_OF_ROM.zip /sdcard/"
6. Install zip from sdcard->choose the zip->done.
kyokeun1234 said:
Use adb push.
1. Download ROM of your choice
2. Place it in the same directory as adb.exe
3. Boot your (SuperWiped) phone into recovery mode (Whether it's TWRP or CWM)
4. Open up the cmd in the directory where adb.exe is located
5. "adb push NAME_OF_ROM.zip /sdcard/"
6. Install zip from sdcard->choose the zip->done.
Click to expand...
Click to collapse
Thanks so much! Sorry for all the questions I was just unsure about superwipe. I just did it. I'll let you know later if it works.
Hey guys I get This "Android is Updating" "Optimizing Apps" Window on Every Boot, just for a Few Seconds, It didn't use to do this, has anyone experienced this
It's Really Annoying..
ACtually I Installed The GX Home Launcher MOD and After that this happened to me..
I Read Somewhere about deleting TB.. I Tried That Too.. I Even Deleted 2-3 odex file present in system.. but still not luck.. .. I am using stock ROm.
Any Help Would be Appreciated
ahmedyar91 said:
Hey guys I get This "Android is Updating" "Optimizing Apps" Window on Every Boot, just for a Few Seconds, It didn't use to do this, has anyone experienced this
It's Really Annoying..
ACtually I Installed The GX Home Launcher MOD and After that this happened to me..
I Read Somewhere about deleting TB.. I Tried That Too.. I Even Deleted 2-3 odex file present in system.. but still not luck.. .. I am using stock ROm.
Any Help Would be Appreciated
Click to expand...
Click to collapse
Easiest way imo would be to reflash with the stock rom. use flashtool http://androxyde.github.com/
ahmedyar91 said:
Hey guys I get This "Android is Updating" "Optimizing Apps" Window on Every Boot, just for a Few Seconds, It didn't use to do this, has anyone experienced this
It's Really Annoying..
ACtually I Installed The GX Home Launcher MOD and After that this happened to me..
I Read Somewhere about deleting TB.. I Tried That Too.. I Even Deleted 2-3 odex file present in system.. but still not luck.. .. I am using stock ROm.
Any Help Would be Appreciated
Click to expand...
Click to collapse
I have the same issue, but I am running cm10 146a with gapps from android 4.2. After I installed gapps it begun to do this every boot. But I didn't noticed any problems.
Have you guys cleared cache/dalvik cache? That's like rule number one after flashing
Sent from my LT28at using xda app-developers app
its the mod you have installed
I Hav Been Using This Mod From 2 Months It Never Happened Before.. Actually I Reinstalled The Same Mod And From That Time Its Happening .. But I Dnt Think So This All Happened Becoz Of That Mod..
Or May Be This Mod Has Done Somethng Wrong With Other Thing Which Is Clearing The Cache On Every Boot..
And Yes I Cleared The Dalvik Cache But Its The Same..
Sent from my LT26i using xda premium
ahmedyar91 said:
I Hav Been Using This Mod From 2 Months It Never Happened Before.. Actually I Reinstalled The Same Mod And From That Time Its Happening .. But I Dnt Think So This All Happened Becoz Of That Mod..
Or May Be This Mod Has Done Somethng Wrong With Other Thing Which Is Clearing The Cache On Every Boot..
And Yes I Cleared The Dalvik Cache But Its The Same..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
I think it has to do with the init.d scripts.
Did you add init.d support, then probably the script pertaining to dalvik is the culprit. Remove it and all will be ok.
ganeshbiyer said:
I think it has to do with the init.d scripts.
Did you add init.d support, then probably the script pertaining to dalvik is the culprit. Remove it and all will be ok.
Click to expand...
Click to collapse
I don't Know About "init.d" script.. May This Script Came Up With The Mod..??
Can U Please Tell What Is The Location Of This Script.. I will Look For It..
ahmedyar91 said:
I don't Know About "init.d" script.. May This Script Came Up With The Mod..??
Can U Please Tell What Is The Location Of This Script.. I will Look For It..
Click to expand...
Click to collapse
go to the system folder ..then in the etc folder and then into the init.d folder..
scripts you see with the rwxrwxrwx perms are boot scripts
HIt thanks if this helped u!!!
Try reflashing your kernel! Maybe that would help!
amey_gangal said:
go to the system folder ..then in the etc folder and then into the init.d folder..
scripts you see with the rwxrwxrwx perms are boot scripts
HIt thanks if this helped u!!!
Click to expand...
Click to collapse
There Was No Folder Present With This Name..
Couldn't Find The Solution.. Re flashing The Kernel Was The Last Option...
akkiannu said:
Try reflashing your kernel! Maybe that would help!
Click to expand...
Click to collapse
I also had the same prob b4 its the kernel prob reflash the kernel like @akkiannu mentioned also it that appeared during every boot the phone wont be smooth bt u wont face any other prob.
This is something that's bothered me since upgrading to 4.1.1. Doing just what the title says. So far, I've tried clearing the dalvik cache, wiping the cache partition, uninstalling titanium backup and restarting, as well as uninstalling ROM toolbox and lucky patcher. I'm rooted with chainfire's "quick" method but I also had root before upgrading from ICS. I also tried bin4ry's universal ICS/Jellybean method after upgrading before finding chainfire's, witch, I am suspicious of bin4ry's causing the bug in the first place. The message shows briefly after the glowing "Samsung" boot animation. I have scoured to the bottom of the internet looking for an answer, but I really, really do not want to re-flash the stock rom again. Any reason why this happens? Any way to fix it without wiping my phone; if that works?
Sent from my SAMSUNG-SGH-I747
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Any reasons why this happens?
Mine is doing the same thing.
peneoark said:
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
It's not wiping the dalvik cache. The system displays the message briefly with no application count. I just assumed it was normal on 4.1.1
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Several people seem to claim otherwise, Google shows. My tenant's and several of my friend's phones don't do it. I'll try reverting to factory and upgrading again in a few days if there are no other solutions.
Sent from my SAMSUNG-SGH-I747
Mine showed up after the Google wallet mod. Also had it happen after removing some stock apps although I'm not sure which caused it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've removed a lot of at&t's bloatware, along with S-Suggest, "help" and ypmobile. I've also frozen s-voice and the samsung keyboard in favor of SwiftKey. I've removed bloatware in both so far. Maybe once I revert, I'll try to find out more about the problem. Until my phone is sick of the cache partition wipes and ruthless dalvik cache destruction, I will continue to try in vain. For the good of my OCD.
Sent from my SAMSUNG-SGH-I747
Many ROMs and Kernels are set to ziplalign apps on boot to improve performance.
I want to say this was also implemented in stock JB, or its set in CWM's init.d script for the newer versions.
This also happens each time you wipe dalvik and/or if you have Titanium Backup set to intergrate sys dalvik into ROM
I just did the HOWTO root after upgrading to stock JB, and after reading this post I did a quick reboot and yeh, the message appears for me as well.
Never integrated sysdalvik w/ titanium backup. I've also rebooted the phone without clearing dalvik, and never had cwm. Probably a few things I should have mentioned earlier, but they never crossed my mind.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Fixed the problem. Turns out you do need to re flash the whole phone. Reset to factory in recovery, then wipe the cache AND the dalvik, then reset to stock using ODIN. IT IS IMPERATIVE THAT YOU RESET TO FACTORY. The phone will remain soft bricked otherwise. A tutorial can be found here: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/. The only tried and true way to get the bug out. As far as I know. If anyone has any more ideas as to how this problem occurs, I'd still like to hear them.
Sent from my rooted SAMSUNG SGH-I747. THANKS CHAINFIRE!!
I rarely reboot these days. I do my CWM backups online.
But when I do reboot, I do get that updating message and have been seening that from as far back as I can remember. It bugged me at first but not now. For me, it only does it for about 2-4secs so I don't bother trying to fix it.
I have the cause in my case but I don't have the solution. I flashed a mod I found here http://forum.xda-developers.com/showthread.php?t=2044449, apn_editor_1.1.zip. Now every reboot I get Android Is Upgrading.... Starting apps.
How do I stop the phone from trying to add this mod?
Just got the same problem. Had super SU on the phone (soft root), so i tried to fully root (i installed xblasttools, and had to flash pa-icons, so i could change the color of the battery, but i couldn't because it said signature failed). Downloaded philz kernel/root, flashed with recovery. Then i uninstalled the Super su rebooted and there it was; Andriod is upgrading ...
I'm on 4.1.2, Samsung GT-i9100. Help !
P.S Uninstalled the superuser that i got with the phil kernel and installed Super SU. Also i did wipe the davlik and cache. Same stuff.
I got the Android is upgrading message before. It was because I tried to convert a user app to a system app. Converted it back to a user app and it went away. I think it had something to do with having an apk file but no corresponding odex file for that app in /system/app
Sent from my SGH-I747M using xda app-developers app
I have found why this happens, issue is with lucky patcher, when you patch application it creates <appname.odex> this odex file is somehow diffrent than real odex, so when you wipe dalvik cache it caches all your apps and then you have Android is starting apps on each boot. The solution is to delete all apps odexes wich you patched, reboot phone, this time it will not display "android is starting apps" and will work until you delete dalvik again. It is possible to apply patch with Lucky Patcher to dalvih cache instead of creating odex, but you loose your crack when you wipe dalvik again.
This is the solution, if someone have better way of doing it post here, also sorry if thread is old.
magix01 said:
I have found why this happens, issue is with lucky patcher, when you patch application it creates <appname.odex> this odex file is somehow diffrent than real odex, so when you wipe dalvik cache it caches all your apps and then you have Android is starting apps on each boot. The solution is to delete all apps odexes wich you patched, reboot phone, this time it will not display "android is starting apps" and will work until you delete dalvik again. It is possible to apply patch with Lucky Patcher to dalvih cache instead of creating odex, but you loose your crack when you wipe dalvik again.
This is the solution, if someone have better way of doing it post here, also sorry if thread is old.
Click to expand...
Click to collapse
Thank you for pointing out Lucky Patcher. The "android is starting apps" notification started when I deodexed my rom. I uninstalled those patched apps, reinstalled and re-patched normally with Lucky Patcher 3.9.9.1 and that notification is gone.
:good:
coffee black said:
Thank you for pointing out Lucky Patcher. The "android is starting apps" notification started when I deodexed my rom. I uninstalled those patched apps, reinstalled and re-patched normally with Lucky Patcher 3.9.9.1 and that notification is gone.
:good:
Click to expand...
Click to collapse
Next time just cut odex files to other location, reboot phone and copy odexes back, this should be alot easyer
Try to reflash your rom that may help some how
Sent from my GT-I9500 using xda app-developers app