12-20-2014 12:26 AM
35 12
tools
  1. apoc53's Avatar
    The solution is either install a custom ROM or learn to love 3-minute bootups. Do NOT root your phone on the advisement elsewhere that it will fix the problem (the problem, by the way, being that the dalvik cache where optimizations are stored is wiped any time you shut down or reboot the phone). While rooting isn't necessarily a bad thing - and is the first step in loading a custom ROM, should that be your choice - it is NOT a fix in and of itself, it voids your warranty, and it can lead to other issues that may require a heightened technical competence to correct.

    Sent from my HTC PH39100 using Android Central Forums
    10-31-2012 07:58 PM
  2. OperationA7X's Avatar
    The solution is either install a custom ROM or learn to love 3-minute bootups. Do NOT root your phone on the advisement elsewhere that it will fix the problem (the problem, by the way, being that the dalvik cache where optimizations are stored is wiped any time you shut down or reboot the phone). While rooting isn't necessarily a bad thing - and is the first step in loading a custom ROM, should that be your choice - it is NOT a fix in and of itself, it voids your warranty, and it can lead to other issues that may require a heightened technical competence to correct.

    Sent from my HTC PH39100 using Android Central Forums
    Correction: "Rooting can give you trouble...when used/done incorrectly."

    However, he does have a point. Rooting is not really the answer, a whole new ROM is the solution. You see, when you shutdown the Vivid after the ICS upgrade, it does wipe the Dalvik-Cache. I guess this was HTC's attempt at keeping the system memory free, but forces the phone/OS to regenerate the cache on boot, or the "Dalvik". So, either get used to "fastboot" (Settings>Power>Check Fastboot), just deal with the time, or customize your phone. Good luck.
    10-31-2012 08:39 PM
  3. apoc53's Avatar
    Not sure what you mean by "get used to fastboot", but since you're allergic to stock ROMs you may not have seen this problem in-depth . I've run with Fastboot on and off, and either way, the cache always rebuilds on boot. I've noticed a few situations where it doesn't, but those cases may have been when the battery was pulled (system didn't have time to clear the cache on shutdown, perhaps?). Haven't probed any deeper into that, though.

    Sent from my HTC PH39100 using Android Central Forums
    10-31-2012 10:49 PM
  4. OperationA7X's Avatar
    Not sure what you mean by "get used to fastboot", but since you're allergic to stock ROMs you may not have seen this problem in-depth . I've run with Fastboot on and off, and either way, the cache always rebuilds on boot. I've noticed a few situations where it doesn't, but those cases may have been when the battery was pulled (system didn't have time to clear the cache on shutdown, perhaps?). Haven't probed any deeper into that, though.

    Sent from my HTC PH39100 using Android Central Forums
    I do...I started from the stock up. And let me explain clearly how "fastboot" works: Ever heard of the "Hibernate" function on a Windows/Unbuntu computer? It's essentially that. It basically caches the system into the memory. However, not the whole system, but about 90% of it. So, there's only a 30 second boot up time. But it also saves the system to RAM. Long story short, of course it won't work if you pull the battery. You can say I'm inexperienced with stock ROMs, but that's how I learn a phone. After FULLY learning stock, I mod, customize, root, change partitions, etc. And pulling the battery without shutdown really doesn't help or hinder anything. So please, do you have any other questions or comments to/for me?
    11-03-2012 05:28 PM
  5. vividrich's Avatar
    Usually on fastboot it won't rebuild, which I wouldn't expect it to...every once in awhile it will though even on a 'fastboot' startup. Any idea why?

    Sent from my HTC PH39100 using Android Central Forums
    11-03-2012 07:01 PM
  6. apoc53's Avatar
    Not attacking you, if that's how you took it (saw some recent attacks on one of your first posts, but I'd say you've more than proven yourself since then). The reason I've never seen Fastboot work as designed may be that I never shut the phone off, only reboot. The whole point of a reboot is usually to clear misbehaving software, which wouldn't happen if a reboot threw everything to RAM, then reloaded it all on the way back up. Either way, custom ROM seems to be the only real fix for this problem.

    Sent from my HTC PH39100 using Android Central Forums
    11-03-2012 09:59 PM
  7. OperationA7X's Avatar
    Usually on fastboot it won't rebuild, which I wouldn't expect it to...every once in awhile it will though even on a 'fastboot' startup. Any idea why?

    Sent from my HTC PH39100 using Android Central Forums
    The system storage space only has so much room, eventually, it would need to rebuild. But that's only my assumption.
    vividrich likes this.
    11-04-2012 02:18 AM
  8. OperationA7X's Avatar
    Not attacking you, if that's how you took it (saw some recent attacks on one of your first posts, but I'd say you've more than proven yourself since then). The reason I've never seen Fastboot work as designed may be that I never shut the phone off, only reboot. The whole point of a reboot is usually to clear misbehaving software, which wouldn't happen if a reboot threw everything to RAM, then reloaded it all on the way back up. Either way, custom ROM seems to be the only real fix for this problem.

    Sent from my HTC PH39100 using Android Central Forums
    Well, yeah, the "fastboot" option is a low-level selection, meaning it's system installed. How to tell the difference: In normal mode: Just press the power button to boot, wait a few minutes. In fastboot mode: Hold down power button to turn on, can't get to HBOOT with it enabled, takes about 30 seconds to boot. It needs to save the system to memory, so that's why it needs to shut down, if you just reboot, it's pretty much useless.
    11-04-2012 02:21 AM
  9. danny sadler's Avatar
    Mine started this right after I installed link2sd so I figured that was the reason. But sometimes it will sat 1out of 121 application and I don't have that many.
    03-12-2014 02:14 AM
  10. LovelyLeslie's Avatar
    Phone is stuck in "Android is upgrading. Optimizing application 1 of 1" HELP!!!!!!!!!!!!!

    i remember i was downloading something from google play store but it took so long so i cleared cache from playstore then i also used clean master and du booster to clean junk but it was taking longer than usual also so i stopped my downloads and everything i was doing.

    i powered off my phone. then turned it on again and it says

    "Android is upgrading, Optimizing application 1 of 1"

    and i already slept for more than 8 hours and its stuck there. I cant do anything except remove my battery,sim and sd card.

    help me please....
    12-20-2014 12:26 AM
35 12
LINK TO POST COPIED TO CLIPBOARD