I recently flashed the Super_Z2.4 rom, was running SR3.5. I have now developed an issue where Titanium force closes, the app will not even start. I have re-installed Titanium several times, thinking I may have a corrupt download, and even downloaded an older version from the dev's web site. I never had this issue with any of the SR roms, never had this problem at all. I am still tunning the kernel that came with the Super_Z rom. Any thoughts, ideas, or suggestions would be great. Thank you.
Couple things to try:
Clear the cache for the TB app. Settings>Applications>Manage Applications>Downloaded>TB - clear data and cache.
and/or
Uninstall TB, boot into recovery, run fix permissions from recovery, clear cache in recovery, clear dalvik in recovery, reboot, d/l TB from market.
I already tried running the fix permissions, from both Rom Manager and by rebooting into Clockwork. I just flashed back to my nandroid of SR3.5 and TB works perfectly there. I'm not sure if it is a rom issue or a kernel issue. I'm gonna PM the dev of the Super_Z rom and ask him, as I am not yet able to post in the dev forum to ask there.
Just flashed back to Super_Z and tried clearing the cache for TB, no dice....
Wow .... sounds like a ROM thing.
Sent from my ADR6300 using XDA Premium App
Hello potential helpers in the CM community.
So long full days work or android updating story short, I was running 7.0.2.1 and updated to 7.0.3 with rom manager. I decided to not wipe all data, but to just clear the dalvik cache. After the update all the apps tried to reinstall again. I tried to do a titanium backup restore on top of that and everything froze up. I rebooted and tried again. Same thing happened. So i reverted to the nandroid 7.0.2.1 and did the entire thing over again but this time wiped the cache, and the same thing happened. So I wiped the data and cache, did a nandroid restore to the original 7.0.2.1 and then tried to do some different options. i changed up th order in which I did a restore, what cached I cleared, and anything I could think of. But Now I am stuck at either my nandroid 7.0.2.1 or 7.0.3. Both of these ROMs work fine with no issues EXCEPT whenever I try to install an app it fails. I have cleared the market app data and cache, but nothing seems to work. Any ideas?
Thanks
2 things.......
1. You should have posted this in the CM7 thread.
2. I would try reloading a fresh market .apk and see if that takes care of your issue. Usually just clearing cache and data will take care of those issues.
Sent from my CM7 Droid Incredible using XDA App
Also its good to make it a habit to flash ROMs in recovery after a cache and dalvik wipe instead of using RM
Sent from my CM7 Droid Incredible using XDA App
I will try that
Firstly, sorry have not been on XDA scene cm7 was out, didnt even check for that, and secondly I will try that. Thanks for the tips
justinmburrous said:
Firstly, sorry have not been on XDA scene cm7 was out, didnt even check for that, and secondly I will try that. Thanks for the tips
Click to expand...
Click to collapse
NP good luck, hopefully re-flashing market fixes your issues. You can find the .apk floating around XDA. Let me know if it work.
fixed
So I ended up just reverting back to the nandroid and then flashing 7.0.3 before I reflashed the market. However the market worked fine right after reflashed the new version of CM. I did not change anything from what I did in the past, but it is fixed. Thanks for your. help.
justinmburrous said:
So I ended up just reverting back to the nandroid and then flashing 7.0.3 before I reflashed the market. However the market worked fine right after reflashed the new version of CM. I did not change anything from what I did in the past, but it is fixed. Thanks for your. help.
Click to expand...
Click to collapse
Anytime. Glad everything is back to normal.
The last few months I've been experiencing an issue where I'll install a new rom after wiping data, cache, and dalvik with everything running smoothly and them after two weeks I get constant FCs. Happened after CM 7, gingerbread debloated, and sky raider. Would formatting the device solve the issue or is that overkill?
Sent from my Transformer TF101 using xda premium
Format everything in the mounts and storage menu in recovery except sdcard and emmc. Also wipe dalvik cache from the advanved menu. It is a good idea to do this before installing any rom or before restoring a nandroid backup.
It could also be a certain app your using that is messing things up. What exactly fc's is it certain apps all the time or just a bunch of different apps randomly?
I just did my first custom ROM installment yesterday and well it was nice for a couple of minutes... All of a sudden my messaging and wallet app started force closing constantly every other 5 seconds. Along with something called android.process.acode (not sure if that's what it was called but it's what i remember).
Yes I backed up all my data (titanium pro and CWM), cleared cashe and dvalink or whatever the heck it's called. I then installed the ROM from zip and everything went smoothly, even installing GAPPS.
I was upgrading from stock 4.0.2. I'm not sure if i installed the correct version of GAPPS for it though so maybe that's the problem? Idk what else I should do, maybe just a new ROM?
Thanks in advance!
anyone? bump...........
SikkNazty said:
I just did my first custom ROM installment yesterday and well it was nice for a couple of minutes... All of a sudden my messaging and wallet app started force closing constantly every other 5 seconds. Along with something called android.process.acode (not sure if that's what it was called but it's what i remember).
Yes I backed up all my data (titanium pro and CWM), cleared cashe and dvalink or whatever the heck it's called. I then installed the ROM from zip and everything went smoothly, even installing GAPPS.
I was upgrading from stock 4.0.2. I'm not sure if i installed the correct version of GAPPS for it though so maybe that's the problem? Idk what else I should do, maybe just a new ROM?
Thanks in advance!
Click to expand...
Click to collapse
Did you wipe dalvik and /cache only?
Need to wipe /data (factory reset) and /system (just for good measure) then re-flash your ROM/Kernel/Gapps
Sent from my Galaxy Nexus using Tapatalk
_Dennis_ said:
Did you wipe dalvik and /cache only?
Need to wipe /data (factory reset) and /system (just for good measure) then re-flash your ROM/Kernel/Gapps
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
yes i did wipe data, forgot to mention that. I just found out it was because of the wrong version of gapps. Thanks anyways dude!
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