I have seen some threads from a month ago but does anyone else still have really long boot times on CM10?
I'm talking like almost 5 minutes probably to boot up the phone.
It happens whether I pull the battery or just do a soft reboot from the menu.
I've always had it but I have upgraded to the newest bootloader that I know about and it is still happening?
Half of the boot is spent at the google bootloader screen and half is on the CM10 boot screen.
Is everyone else getting the same thing or is it just me?
That's definitely abnormal. I've never experienced boot times nearing that long, even after a clean flash, or flashing from a different ROM.
I'd try a completely clean install, including formatting /system.
Edit: a logcat would likely point to the problem if it remains.
CMNein said:
That's definitely abnormal. I've never experienced boot times nearing that long, even after a clean flash, or flashing from a different ROM.
I'd try a completely clean install, including formatting /system.
Edit: a logcat would likely point to the problem if it remains.
Click to expand...
Click to collapse
Definitely abnormal. I would say mine is booted in under 30 seconds. 40 if its a long boot. I agree run a logcat and see what it says
Try logcat or /proc/kmesg indeed. First time boot after wiping Dalvik cache takes more time since Android needs to rebuild it, but after that it should boot normal.
Related
Over the last few months, I have noticed that my phone tends to get stuck on the splashscreen ALOT. I notice it when I reboot the phone. I can't remember it really ever being like this.
Someone did make a custom boot screen (The Michael Jordan symbol by Rydah in the Theme's and App forum.) I am in no way saying it's this or his fault or anything, I just have noticed it happening a lot sometime after I added that file.
I have flashed a lot of rom's here and there (always wiping ALL and using the format.all 2x before flashing a new ROM.)
I was wondering if anyone else has encountered anything like this and if they were able to correct it somehow? Or, if anyone has any suggestions on what I can do to try and correct this so anytime I reboot, it reboots normally instead of locking up?
BTW, when it locks up, I do the battery pull and let the battery sit for 30 seconds before I put the battery back in and reboot.
Thank you,
Whiteice
Well the phone will take slightly longer to boot up once you wipe the caches, because they have to rebuild. Do you wipe your cache and dalvik when flashing a boot animation?
WhiteiceDMSTech said:
Over the last few months, I have noticed that my phone tends to get stuck on the splashscreen ALOT. I notice it when I reboot the phone. I can't remember it really ever being like this.
Someone did make a custom boot screen (The Michael Jordan symbol by Rydah in the Theme's and App forum.) I am in no way saying it's this or his fault or anything, I just have noticed it happening a lot sometime after I added that file.
I have flashed a lot of rom's here and there (always wiping ALL and using the format.all 2x before flashing a new ROM.)
I was wondering if anyone else has encountered anything like this and if they were able to correct it somehow? Or, if anyone has any suggestions on what I can do to try and correct this so anytime I reboot, it reboots normally instead of locking up?
BTW, when it locks up, I do the battery pull and let the battery sit for 30 seconds before I put the battery back in and reboot.
Thank you,
Whiteice
Click to expand...
Click to collapse
That's never really happened to me on a consistent basis. I've got stuck at the splash screen a couple of times, but it was my own doing one way or another. How long do you let it hang on the Splash screen before you pull the battery? Sometimes mine will sit on the splash for a good minute or so during a normal reboot. After wiping cache's it can sit there for a good 3 or 4 minutes sometimes. I've caught myself pulling hte back cover off the phone to yank the battery, then I notice that the boot animation was starting, and it booted up. I just wasn't patient enough. Have you tried changing away from that boot animation, temporarily, to see if the problem goes away? I doubt that's the cause, but you never know. And if it started happening right when you changed boot animations, I'd say the first thing to try would be changing out to a different one, and see if the problem persists. Has this been happening on any ROM/Kernel combo you've tried? Perhaps it's the kernel you're on, have you tried another? Do you use SetCPU?
Thank you for the responses.
Just to make sure, it is not the boot animation but the splash screen (Originally the white screen that had EVO on it) that I have changed.
The boot animation screens are usually the ones that comes with whatever ROM I am using. I have done the particle motion boot animation from time to time.
And, anytime I flash I flash in recovery, I always ALWAYS wipe cache and dalvik cache (Unless I am flashing a new ROM, then I wipe everything 2x prior to flashing it.)
I usually let the splashscreen sit for about a minute, maybe 2 if that. I was under the impression that if the splashscreen sits there for more then a minute, then I should battery pull to fix it?
I use different kernels to try them out depending on if I am using a sense based or AOSP rom, and it seems to happen no matter what kernel. I do not use SetCPU.
Whiteice
WhiteiceDMSTech said:
Thank you for the responses.
Just to make sure, it is not the boot animation but the splash screen (Originally the white screen that had EVO on it) that I have changed.
The boot animation screens are usually the ones that comes with whatever ROM I am using. I have done the particle motion boot animation from time to time.
And, anytime I flash I flash in recovery, I always ALWAYS wipe cache and dalvik cache (Unless I am flashing a new ROM, then I wipe everything 2x prior to flashing it.)
I usually let the splashscreen sit for about a minute, maybe 2 if that. I was under the impression that if the splashscreen sits there for more then a minute, then I should battery pull to fix it?
Whiteice
Click to expand...
Click to collapse
Oh I gotchya, so it was the splash screen you changed to the jordan symbol. Yea, I mean, most of the time it will pass by the splash screen in less than 30 seconds, but for whatever reason, from time to time it will sit in the splash for a little longer than normal. If it goes past 5 minutes then yea, that's too long. It shouldn't take that long. Have you tried a different kernel?
Yes, I try different kernel's all the time and it happens on most of them.
It seems that anytime it freezes up on the splashscreen and I reboot, and it still freezes up on the splashscreen that I have to reboot into recovery (AMON 2.3) and wipe cache and delvik cache each and every time for it to clear whatever is going on. Then usually it reboots fine the next boot after doing that until I reboot again and it locks up. Then repeat above.
Thank you,
Whiteice
I just got my EVO last Friday and after i rooted i noticed that sometimes not all the time... it takes a long time for it to get from splash screen to boot screen. Is it normal for it to last over 1 min in splash at times? Ive tried several roms and all do the same.
Nothing to worry about, unless it never boots up. Your ok, mind does this too at times
robert00693 said:
I just got my EVO last Friday and after i rooted i noticed that sometimes not all the time... it takes a long time for it to get from splash screen to boot screen. Is it normal for it to last over 1 min in splash at times? Ive tried several roms and all do the same.
Click to expand...
Click to collapse
Yea, boot times vary. Any time after you wipe cache/dalvik cache, the system takes a lot longer to boot up, due to the fact that it needs to rebuild the dalvik cache. Sometimes a specific kernel you're on can cause boot times to vary, in my experience. Also, I remember reading that deodexed roms take a little longer to boot (all the custom roms, for the most part, are deodexed. A stock rom is Odexed, and boots quicker) But, as the other guy said, as long as it boots up I wouldn't worry about how long it takes to boot up. You should be good.
hey guys, my problem is that my recovery freezes after 10 or 15 seconds. it was all good until 3 month ago when randomly start to freeze. now it doesn't matter which recovery im using (i tried all of them) it freezes. sometimes i reboot to recovery and it works fine and i can flash a rom or whatever i want to do, but most of the times it freezes.
i tried wiping everything several times, including internal storage and even external storage.
at the moment every time that i want to try a new rom i need to spend about 30 min rebooting over and over again until i can flash the rom. if is an action that last less than 10 or 15 seconds is all good, like flashing another recovery or just wiping cache, but long actions like flashing gaps or rom it doesn't work cause it takes more than that.
im not an expert on android but the only thing that i can think on is that even wiping everything there is still a file or something that is [email protected](#ing with the recovery, but i don't know maybe my phone is f^(#ed.
please help, i don't want to get another phone, i love this one.
by the way, is a note 2 GN7100 international.
thanks
I run a rooted SG S3 on stock 4.1.1 with an old 3.0.56 kt747 kernel
Until recently, I've been running this set up for years without any problems.
I've also updated fairly recent CWM along with the latest SU.
As the title states, my phone has been turning off automatically. After weeks of troubleshooting, I noticed a pattern.
When I press the power button, there are three different scenarios that happen.
The phone goes to sleep normally
The phone goes to sleep and immediately wakes up to the lock screen
The phone displays the shut off menu
If scenario 1 occurs, everything is fine and runs perfectly for an indefinite amount of time until i attempt to put the phone to sleep again.
but, if scenario 2 or 3 occurs, the phone automatically shuts down abruptly, within 1-5 seconds.
This problem still occurs even when I boot into safe mode, and I have eliminated the SD card as a suspect. Furthermore, booting the phone up has become extremely difficult. The boot would sometimes crash after the samsung logo, after the splash screen, or during the boot animation. It takes somewhere around 3-5 tries to fully boot up the phone.
Booting into CWM recovery is still possible, but even that sometimes crashes mid-way. I've also noticed that at certain times, when I click the power button to select an action in CWM, it actually double clicks (thankfully CWM is tolerant to that) and cancels the action I was trying to do. I've done some googling and found that an over sensitive power button is a common occurrence in this model, and while that may explain why the 3 different power button scenarios occur, it still doesn't explain the crash.
Finally, I seemed to have remedied the automatic shut off problem several times by wiping cache from CWM. When I first started having these problems and began troubleshooting, wiping the cache eliminated the problem for about a week before the problem came back. When it did, I uninstalled some apps and re-wiped the cache which eliminated the problem again for several days. However, these periods become shorter and shorter, and now wiping cache does not seem to help at all. I've also tried wiping the delvik cache, but it didn't help.
I'm stumped right now. Any suggestions would be appreciated before I try some more large-scale attempts such as resetting my phone or taking it apart. Thanks everyone!
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
jason2678 said:
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
Click to expand...
Click to collapse
Yeah, that's part of the reason why i didn't want to upgrade the bootloader for the newer firmwares. I messed around with my phone this morning and its been avoiding the problem ever since. Not exactly sure what I did though lol. Thanks for the reply, I'll try it if the problem comes back over the next few days.
Your phone isn't "crashing," your power button is malfunctioning. The fix is pretty easy. You will need to open your phone up and scrape it off (the phone can be turned on without it). There are youtube videos that show how to remove it.
Since not so long ago I've experienced the following:
If I leave the phone two have low battery like 10% when it dies it enters a boot loop I cannot stop and I just can only plug it in and wait while it bootloops without being able to stop it and a long time later (20/30 min) it will finally boot up, last time it had 30% battery when it finally booted up.
What could it be? It may have been the last update? Has anybody experienced this?
If you did a major firmware upgrade without a factory reset, do a factory reset now.
Otherwise clear the system cache.
It it persists, factory reset.
If it still continues it maybe hardware. It could be corrupted firmware but trying to reflash may end up causing it to brick if it acts up during the reflash. Consider your options carefully at this point especially if under warranty or insured.
I have the same thing. The phone just starts to vibrate indicating a startup, then after a few seconds it vibrates again, and continues in this loop. The screen doesn't display anything.
I'm having the same thing right now, I tried wiping the cache from bootloader and charging the phone to 100%, but it doesn't seem to be fixed
Maybe on an unlocked bootloader it doesn't work? Something related to offline charging?
IronHulk27 said:
I'm having the same thing right now, I tried wiping the cache from bootloader and charging the phone to 100%, but it doesn't seem to be fixed
Click to expand...
Click to collapse
I have not had it happen lately the other day I had 5% battery and it worked fine.
I think it might be an unsupported charger?