• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

2 years with this a phone and now just asking this

J

jrsharp21

Newbie
why does it take so long to boot up?

When the phone first starts it goes to the Galaxy S3 logo, then to just the blue swirl Samsung logo, then to the AT&T logo and plays the AT&T chime, then goes to PIN log in for encrypted device memory (I think this is a work thing), then to the green Android guy, then to the Samsung logo again, and then to th AT&T logo again. It seriously takes almost a full minute to 90 seconds to boot up the phone. Any suggestions?
 
Wow, the wife's S3 (not encrypted or pin locked) doesn't go through near that many steps or take so long. I think its Samsung, boot animation, VZW logo, and she is at the unlock screen. ~20-30 seconds. I would guess the encryption would slow it down and introduce the pin stage, but it sounds almost like you have a bootloop in there.:confused:
 
I'm guessing the encryption is to blame. While I was experimenting with device encryption on my phone, I found that it was pretty much half a boot cycle before it would get to the encryption PIN/password prompt. Once past that, the phone essentially has to perform a hot-reboot (to reinitialize everything from the encrypted partition).

I'm not sure that there's much you can do to speed it up. :(
 
Thanks guys. This has been one part of the S3 has really bugged me and has me thinking of going to a iPhone 6+. Our company has no Android knowledge in the IT department. Everything they support is Apple or Blackberry. I think I was the first guy to ditch the iPhone and go Android a few years ago.
 
A factory reset (deleting all your userdata and applications in the process) can sometimes help to speed up the boot process a little - though the company-mandated encryption means that it will never boot as quickly as a stock device.

If you're ready to throw down dollars for a new iPhone 6+, why not put that towards a newer (and more capable) Android device?
 
My s3 running a pretty lean aosp based rom takes forever to boot.... maybe even 3minutes (or thats how it feels) but i only really reboot it in the morning when changing battery so its not much of an issue for me tbh
 
funkylogik said:
My s3 running a pretty lean aosp based rom takes forever to boot.... maybe even 3minutes (or thats how it feels) but i only really reboot it in the morning when changing battery so its not much of an issue for me tbh
Click to expand...

Hey...what's the advantage of booting each day? I NEVER boot unless I'm having some sort of difficulty.

JM
 
javamann said:
Hey...what's the advantage of booting each day? I NEVER boot unless I'm having some sort of difficulty.

JM
Click to expand...
It clears out a lot of useless data and resets long running useless processes. Very good idea for any wireless device.
 
javamann said:
Hey...what's the advantage of booting each day? I NEVER boot unless I'm having some sort of difficulty.

JM
Click to expand...
Me neither. My OG Droid has been running nonstop for 2+ years and the only reason it was restarted is I knocked it off the base and the battery went dead. In fact the uptime counter resets itself after a year.;) IMO it ain't Windows. A process get's killed, the memory will get cleared out when needed by something else.
 
Mine boots in 30 seconds or so, but if I want to actually lock the screen and have the light keys light up I have to wait until it says "power saving mode activated"... which can take up to a minute at most.
 
You must log in or register to reply here.
Back
Top Bottom