Related
What could bw causing this to happen? Please help.
Sent from my PC36100 using Tapatalk
I would say re-flash your rom, wipe cache and dalvik, and flash the latest gapps.
Sorry didn't say before but everything is stock
Sent from my PC36100 using Tapatalk
So not rooted...Its even closing after you reboot?
I would try going into applications, clearing the cache, force stop it, reboot, then try again.
teh roxxorz said:
So not rooted...Its even closing after you reboot?
I would try going into applications, clearing the cache, force stop it, reboot, then try again.
Click to expand...
Click to collapse
If you are still FC'ing after this, try doing a factory reset, and if that doesn't fix it, i recommend taking it into a sprint store.
You should also make sure that you have a data connection where you are located, because the market will FC if you don't have data (3g/4g/wifi).
Yes and I've done that also I want to do everything before going to sprint and having to reset it
Sent from my PC36100 using Tapatalk
princessakiki said:
Yes and I've done that also I y1085 to do everything before going to sprint and having to reset it
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Like the other user said, you can do a factory reset.
Turn your phone off. Hold the vol+down button while turning it on, and you'll be in the bootloader, a white screen with androids on skateboards. Use vol+down to scroll down to clear storage, then use the power button to select. Factory reset done.
Not sure if it's just me or the phone. I'm currently running RCMix3d Runny v4.0, which I love, it's great. But I wanted to try AOSP to get a more natural feel. I installed CM7, had problems connecting to network and tons of FC's. Went back to RCMix3d, for a few days, then decided to try MIUI. Looks smooth, nice features. Tried to change some settings (turn on BT, turn on unknown sources install), phone did a Hot boot, once it came up I get constant android.process.acore FCs.
Both times installing AOSP roms I did a format data/cache/dalvik, not just installing over RCMix3d. Even tried doing format x2 on all first.
Anyone else having similar problems, or could it just be something I'm doing wrong?
Thanks
NYCBest said:
Not sure if it's just me or the phone. I'm currently running RCMix3d Runny v4.0, which I love, it's great. But I wanted to try AOSP to get a more natural feel. I installed CM7, had problems connecting to network and tons of FC's. Went back to RCMix3d, for a few days, then decided to try MIUI. Looks smooth, nice features. Tried to change some settings (turn on BT, turn on unknown sources install), phone did a Hot boot, once it came up I get constant android.process.acore FCs.
Both times installing AOSP roms I did a format data/cache/dalvik, not just installing over RCMix3d. Even tried doing format x2 on all first.
Anyone else having similar problems, or could it just be something I'm doing wrong?
Thanks
Click to expand...
Click to collapse
You may wanna format system as well.
Sent from my Incredible 2 HD using "Iced Frosting" Tapatalk
tylerlawhon said:
You may wanna format system as well.
Sent from my Incredible 2 HD using "Iced Frosting" Tapatalk
Click to expand...
Click to collapse
Sorry, what do you mean format system? I'm doing from CWM, wipe data/factory reset, wipe cache partition, wipe Dalvik Cache.
Unless you meet from the boot menu, doing a factory reset (which i'll need to reroot)
NYCBest said:
Sorry, what do you mean format system? I'm doing from CWM, wipe data/factory reset, wipe cache partition, wipe Dalvik Cache.
Unless you meet from the boot menu, doing a factory reset (which i'll need to reroot)
Click to expand...
Click to collapse
No, don't do that. In CWM, go to mounts and storage. You'll see format system, run that. Then wipe data/factory reset in the main CWM screen. Then install your AOSP ROM.
Sent from my Incredible 2 HD using XDA App
tylerlawhon said:
No, don't do that. In CWM, go to mounts and storage. You'll see format system, run that. Then wipe data/factory reset in the main CWM screen. Then install your AOSP ROM.
Sent from my Incredible 2 HD using XDA App
Click to expand...
Click to collapse
Ah right, I forgot that was under mounts. Thanks.
NYCBest said:
Ah right, I forgot that was under mounts. Thanks.
Click to expand...
Click to collapse
Lemme know if it works, and don't feel shy around the thanks button
Sent from my Incredible 2 HD using "Iced Frosting" Tapatalk
Well, I'm just an idiot. So I did the system format, still had same issues with MIUI.
Noticed that the issues start right after I restore from Titanium backup. Then realized I was hitting Restore System + Apps. Which going from Sense to AOSP, doesn't work so well.
Just reinstalled and only restored Apps. Working fine now.
Thanks for the help!
Sometimes the easiest things are the ones most overlooked!!! (been there done that.....way toooo many times..lol)
Glad ya got it going!
I've used Cyanogen Mod for quite a while without issue. Then, last week my camera started force closing. So far as I knowing didn't change any settings or install an app that would mess with it. Haven't updated radios, etc...it just stopped. I've cleared the cache in apps settings, there is space on the card.
Any suggestions? Thanks!
clear cache and dalvik from recovery, and reboot. If that doesnt work, you will probably have to reflash the rom.
sitlet said:
clear cache and dalvik from recovery, and reboot. If that doesnt work, you will probably have to reflash the rom.
Click to expand...
Click to collapse
Do I need to back anything up before doing this? Thanks.
Sent from my PC36100 using Tapatalk
polkadots said:
Do I need to back anything up before doing this? Thanks.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Shouldn't lose anything, as you are just clearing cache files. However, it can never hurt to do a backup first, only takes a couple minutes.
Ugh. I did a full wipe and upgraded to 7.1 (was on 7.0.2)...Camera is still FC'ing...again, it works with other apps (Vignette, Goggles) but not the stock camera. It worked just fine until two weeks ago...and then, nothing. No clue why. :/
Well, now it works...I did one more wipe and it just started working. Thanks!
Try fix permissions, worked for me
Sent from my PC36100 using xda premium
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
Hey all, so I flashed the chemistry ROM and Goodness 8.0.3, which both have multi window. After I try to power on my phone after a full shut down, neither ROM seems to boot without me going into recovery and clearing both cache. Anyone else experience this or have a workaround?
Sent from my SPH-L710 using Tapatalk 2
Were they clean flashes?
Sent from my PG06100
CNexus said:
Were they clean flashes?
Sent from my PG06100
Click to expand...
Click to collapse
Yes, both done after a full wipe (minus internal SD card).
Sent from my SPH-L710 using Tapatalk 2
dante32278 said:
Hey all, so I flashed the chemistry ROM and Goodness 8.0, which both have multi window. After I try to power on my phone after a full shut down, neither ROM seems to boot without me going into recovery and clearing both cache. Anyone else experience this or have a workaround?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I just had the same issue I installed chemistry on my phone worked with no problems but on my moms phone i went into a bootloop after rebooting. I had to go into recovery do a factory reset wipe cache and dalvik cache and reflash the Rom all seems to be working now. Oh it was chemistry v5 btw.
Edit
Did you retore any system data with TB then hit fix permissions thats what was causing the problem for me.
Ghost8516 said:
I just had the same issue I installed chemistry on my phone worked with no problems but on my moms phone i went into a bootloop after rebooting. I had to go into recovery do a factory reset wipe cache and dalvik cache and reflash the Rom all seems to be working now. Oh it was chemistry v5 btw.
Edit
Did you retore any system data with TB then hit fix permissions thats what was causing the problem for me.
Click to expand...
Click to collapse
I did install non-system apps thru TB and installed latest Ktoonz kernel. Just not sure why either would result in a boot loop now.
Sent from my SPH-L710 using Tapatalk 2
Try flashing a different kernel, and try fixing permissions through rom manager, then reboot wipe cache and dalvik, make it run the optimizing apps thing.
Sent from my SPH-L710 using xda premium