Related
Mine takes 2 mins & 30 seconds.
Starting count during vibration when initially powering on, through the splash screen & boot animation, ending count when the lock screen comes on.
How long does it take yours?
HD87 said:
Mine takes 2 mins & 30 seconds.
Starting count during vibration when initially powering on, through the splash screen & boot animation, ending count when the lock screen comes on.
How long does it take yours?
Click to expand...
Click to collapse
Wow really that long? I just tested it. It was exactly 1 minute from power up to lock screen.
humm .I have never turned.mine off other then going into recovery. So no big deal to me.guessna minute or so
It was exactly 1 minute
42.39 seconds timed with the stopwatch on my phone, vibrate to unlock screen.
To the OP, I'm not sure it should take 2 minutes too boot?!?!?
Yeah thats why I posted this thread.. Im running custom 3.2, richardtrips 3.4 kernel, got bout 1 gig of space left on the internal SD card.. What can cause the boot time to be so long?
HD87 said:
Yeah thats why I posted this thread.. Im running custom 3.2, richardtrips 3.4 kernel, got bout 1 gig of space left on the internal SD card.. What can cause the boot time to be so long?
Click to expand...
Click to collapse
1Gb space left?!?!? What the heck do you have on your tab. I've got tons of apps and have 11.59Gb free.
If a lot of it is music, movies, etc., you might want to store them on your external? Just a suggestion.
Boot up with same set up
Running the Taboonay 2.0 (Android 3.2) and richardtrips 3.4 kernel. Get to the lock screen in 52 seconds. Have 9.51 GB of space left. Maybe not the same ROM. Which custom 3.2?
I have a similar issue, mine takes more than 2 minutes and using stock 3.2 ROM, no mods or anything. Does anybody think his can be caused by an installed app?
I have the same issue, with about 2gb free... Doesn't really bother me though
Sent from my PI39100 using Board Express
sensei22 said:
I have a similar issue, mine takes more than 2 minutes and using stock 3.2 ROM, no mods or anything. Does anybody think his can be caused by an installed app?
Click to expand...
Click to collapse
All the bloatware that comes installed stock on the tab slows it down considerably. What many custom roms do is rip out a lot of the bloatware so there are less running services, which means both a smoother experience while turned on, and faster start-up/shutdown times. Which is why you see some people getting sub-1 minute boots.
@op, what custom rom are you using? You stated that you're using a custom kernal, but if it's not made for the rom you're using, then you can run into problems, a longer boot time more than likely being one of them.
Yes, you are starting something that is causing your problem. However, I would suspect it's something outside the normal apk applications. Normal apk applications are forced to timeout after so many seconds and killed by the engine. So, something taking too long to load normally is killed and you are shown an error about the program. Since you're not mentioning seeing errors, I would suspect an application outside the normal user interface. Just a guess.
In the past, I've seen this were the Linux kernel is trying to init hardware you don't have which waits for a timeout to occur.
I can understand a PC takes a while to boot considering how many different devices it has to set up, but... a nook? It is so simple it should take less than a second to boot.
Any one knows where is most of the time spent during boot?
Thanks
bisbal said:
I can understand a PC takes a while to boot considering how many different devices it has to set up, but... a nook? It is so simple it should take less than a second to boot.
Click to expand...
Click to collapse
What Linux powered devices do you own that boots a cold, non-hibernated, system in less than a second?
In fact the boot sequence on the NST, or any other Android device for that matter, is more or less the same as on a PC, and the device count ain't that different.
The kernel still have to load storage, input, graphics, networking, usb and whatnot.
Hell, one second isn't even enough to finish the bootloader stage
Considering it is a flavor of Linux, probably running those never ending screens of things being started up. As the nook should be an optimized version, it should really go faster. But an unrooted version goes faster than a rooted one, that was one thing I noticed. Maybe running extra services and start up apps.
apeine said:
Considering it is a flavor of Linux, probably running those never ending screens of things being started up.
Click to expand...
Click to collapse
Well, it's running a Linux kernel and the kernel has to load like any other kernel
There's no console output to fb on boot, and even if there was it wouldn't make a dent in the start-up time.
apeine said:
As the nook should be an optimized version, it should really go faster.
Click to expand...
Click to collapse
Faster than what? A PC with 6 - 36 times the processing power?
In fact, the NST kernel loads faster on its puny 800MHz single-core ARM than the 3.0.0-13 kernel on my quad core 2.6GHz AMD.
What we don't see behind that nice boot animation screen is the system that's being loaded on top of the kernel, namely Android and it's Dalvik virtual machine.
If you go trough the logs you'll see that this is where a large portion of the start-up time is being spent
apeine said:
But an unrooted version goes faster than a rooted one, that was one thing I noticed. Maybe running extra services and start up apps.
Click to expand...
Click to collapse
Well simply rooting the NST enables a single tiny service (adbd) and there's no difference in start-up time booting with the stock ramdisk or the adbd enabled one.
I just tested this for the fun of it, and the start-up times are random variations in the order of milliseconds
Now, like you point out, most rooted devices aren't just rooted but have additional services and apps running, and naturally that increased workload would make the device run a little slower based on the amount of additional stuff, and the quality of it
Nice and complete answer, Roger.
Thanks for taking your time to answer that. Maybe the startup time of an unrooted nook was clearly due to extra overhead apps and services. It is quite noticeable, as I did the restore/reset/update/root/restart after fail several times.
Dalvik is the JVM on the android?
apeine said:
Dalvik is the JVM on the android?
Click to expand...
Click to collapse
That's correct
ros87 said:
What Linux powered devices do you own that boots a cold, non-hibernated, system in less than a second?
Click to expand...
Click to collapse
XPUD, boots in 3 seconds and I have a browser ready to use.
bisbal said:
XPUD, boots in 3 seconds and I have a browser ready to use.
Click to expand...
Click to collapse
3 seconds from you press the power button on your pc? Care to share a video of that?
My pc uses 10-12 seconds just to get to the bootloader menu..
Now, aside from that, I've already stated that a large part of the ~30s boot time is spent on loading Android, there's not much that can be done about that.
In this guide I will show you how to speed up Windows 8 Boot time, disabling unnecessary applications
Whats need
-Ccleaner latest version
-PC with Windows 8 :fingers-crossed:
Step 1
-run the program RUN.exe and then we write MSCONFIG and Enter
Step 2
-On the program go to the Services and click Hide all Microsoft services, now stopped some services that not need example: AMD, Google update, Hamachi, utility from manufacturer,Skype updater
Step 3
-Now go to Task Manager, go to startup and disable the unnecessary apps example:Utorrent, apps from manufacturer, Skype, Java
Step 4
-Go to Ccleaner, click Tools and go to Startup and disable apps from Windows-unnecessary, IE-all, Contex menu-all,Scheduled Task.all
Step 5
-Restart the PC and after off and on PC
Boot time
My boot time:
Before: 38 seconds
After: 8 seconds
energymix said:
My boot time:
Before: 38 seconds
After: 8 seconds
Click to expand...
Click to collapse
I find it rather impossible to believe that your windows 8 pc took a whopping 38 seconds to boot.....I may be wrong but I believe that Windows's new system of hibernating the kernel session drastically reduces the boot time to less than 12 seconds.,,38 seconds and 8 seconds sounds like the difference between a windows 7 and windows 8 boot times rather than 2 windows 8 boot times.
mrappbrain said:
I find it rather impossible to believe that your windows 8 pc took a whopping 38 seconds to boot.....I may be wrong but I believe that Windows's new system of hibernating the kernel session drastically reduces the boot time to less than 12 seconds.,,38 seconds and 8 seconds sounds like the difference between a windows 7 and windows 8 boot times rather than 2 windows 8 boot times.
Click to expand...
Click to collapse
I really booted 38-45 seconds because the application is very delayed, but sometimes I booted 8-13 seconds
Yeah... your 38 seconds was a cold boot, your 8 seconds was a hibernation boot. In any case, disabling services and the like doesn't really impact the boot time at all. It may change how long after login before the system becomes responsive, and it can definitely change how much system resources are being used in the background, but the only software ways to reduce the boot time (short of something like hibernation boot) would require removing drivers (as each one of those takes a brief moment to initialize) or using bootloader settings (and most of those are more likely to slow boot times down than speed them up).
GoodDayToDie said:
Yeah... your 38 seconds was a cold boot, your 8 seconds was a hibernation boot. In any case, disabling services and the like doesn't really impact the boot time at all. It may change how long after login before the system becomes responsive, and it can definitely change how much system resources are being used in the background, but the only software ways to reduce the boot time (short of something like hibernation boot) would require removing drivers (as each one of those takes a brief moment to initialize) or using bootloader settings (and most of those are more likely to slow boot times down than speed them up).
Click to expand...
Click to collapse
Exactly.So the name of the guide should be changed to how to impact login times
well even on hibernation boot I need around 30 seconds (but 10 seconds of that contributes to my old BIOS) lol
My new record: 13 seconds. Cold boot. Doesn't get much better than that
Even a layman would know that disabling startup applications can speed up boot time.
Except they don't... Startup apps don't run until the system is already booted, so by definition they cannot impact boot time. On I/O constrained or single-core systems, they make the system essentially unresponsive for some time after bootup, but for something like the Surface RT (4 cores, Flash storage so very wide IO bandwidth) their impact will be minimal.
Hi guys,
I had a question.. My windows 8 used to boot really fast at the beginning on my PC.. But now its taking time.. Almost as much as windows 7 used to take, even during shutdown.. I've actually disabled hibernation function using tune up utilities.. Would this effect booting speed?
Sent from my fingers to your face..!
kishankpadiyar said:
Hi guys,
I had a question.. My windows 8 used to boot really fast at the beginning on my PC.. But now its taking time.. Almost as much as windows 7 used to take, even during shutdown.. I've actually disabled hibernation function using tune up utilities.. Would this effect booting speed?
Sent from my fingers to your face..!
Click to expand...
Click to collapse
How many apps have you installed?
karan128 said:
How many apps have you installed?
Click to expand...
Click to collapse
not much.. 2-3 games and few common apps like vlc, firefox n all those.. no apps from stores..
Disabling Hibernation will not speed up your boot time - quite the opposite, in fact (Win8 likes to do a "hibernation shutdown" where it restarts the computer then immediately enters hibernate, which makes the subsequent bootup very fast). It will have no impact at all on restart time, either (at least, nothing meaningful - possibly a few milliseconds at worst). Hibernate shutdown does indeed take longer (substantially so), but why do you care?
GoodDayToDie said:
Disabling Hibernation will not speed up your boot time - quite the opposite, in fact (Win8 likes to do a "hibernation shutdown" where it restarts the computer then immediately enters hibernate, which makes the subsequent bootup very fast). It will have no impact at all on restart time, either (at least, nothing meaningful - possibly a few milliseconds at worst). Hibernate shutdown does indeed take longer (substantially so), but why do you care?
Click to expand...
Click to collapse
oh okay.. i also wanted to know this.. Sometimes when i keep my system on standby (which i always do), my system wakes up by itself.. then when its not attended for some time it goes to sleep again.. then again in 2 min it repeats.. why is this happening..?
kishankpadiyar said:
oh okay.. i also wanted to know this.. Sometimes when i keep my system on standby (which i always do), my system wakes up by itself.. then when its not attended for some time it goes to sleep again.. then again in 2 min it repeats.. why is this happening..?
Click to expand...
Click to collapse
THis may be happening due to scheduled tasks--
Open cmd and execute this code
powercfg /waketimers
Click to expand...
Click to collapse
see if any task is scheduled to run while pc is on standby..
karan128 said:
THis may be happening due to scheduled tasks--
Open cmd and execute this code see if any task is scheduled to run while pc is on standby..
Click to expand...
Click to collapse
it shows this.. what does it mean..?
PIC: https://www.dropbox.com/s/d3d0cm1ohf5f1hl/cmd.png
kishankpadiyar said:
it shows this.. what does it mean..?
PIC: https://www.dropbox.com/s/d3d0cm1ohf5f1hl/cmd.png
Click to expand...
Click to collapse
Go to "scheduled" task manager and disable that service.(whatever it is, I am not able to see it clearly on my mobile)
Sent from my A9 using xda app-developers app
Windows 8 loads up extremely fast! And I dont think disabling startup apps and services is not necessary, i came across this post, see if it helps you
http://www.computingunleashed.com/speed-up-windows-8-pro.html
my acer S3 ultrabook was using a Seagate 350GB and the boot was super crapy.... I removed the hdd and slot in a Kingston hyper X3 SSD...
my boot time is 7second flat from zero to hero..
best windows OS ever..
my windows surface RT is slowing down a bit after I loaded so many app on it...
Hi, my Thinkpad X230 Tablet boots win 8 in just 6 seconds!
see it in action: youtube
My computer is running UEFI "BIOS" and it has a Crucial mSATA SSD.
A) No, it doesn't. Read up on hibernation boot.
B) This has been discussed before...
Don't get me wrong, it's cool (if you don't mind blowing a ton of disk space for a hiberfile, which is becoming a problem on machines with tons of RAM and tiny SSDs). It doesn't improve reboot time at all though, and I almost never just "turn off" my computer. Why would I? You know what's a heck of a lot faster than a 6-second boot? Instant-on resume from sleep.
HTCalltheway said:
Hi, my Thinkpad X230 Tablet boots win 8 in just 6 seconds!
see it in action: youtube
My computer is running UEFI "BIOS" and it has a Crucial mSATA SSD.
Click to expand...
Click to collapse
It is literally 3-4 seconds on my Toshiba U925.
Oh, and for the record, the full reboot time on my Win8 Enterprise desktop (which has a SSD but no hibernation support because 32 GB of hiberfile would be too much of the SSD) is a little over 20 seconds. Still excellent, and a noticeable chunk of that is due to the computer's old-ish BIOS.
GoodDayToDie said:
Oh, and for the record, the full reboot time on my Win8 Enterprise desktop (which has a SSD but no hibernation support because 32 GB of hiberfile would be too much of the SSD) is a little over 20 seconds. Still excellent, and a noticeable chunk of that is due to the computer's old-ish BIOS.
Click to expand...
Click to collapse
I haven't checked the full boot time when the hibernation support isn't invoked. The screen comes up in around 10 - 15 seconds, and I can log on immediately afterwards, but I've noticed that it isn't really fully up for many more seconds - it appears to be continuing to load various subsystems for up to a minute.
Yeah, all OSes do that. XP and before were awful about it, especially on single-core machines; they tried to load everything at the same time and performance went to crap as a result for a while after login. Vista and later introduced a way to launch services with a delayed start, which improves responsiveness during this period dramatically. I'm not sure what Linux or OS X do, but I've seen the same kind of delay on them too.
Multi-core, high-RAM, and SSD-equipped machines have reduced the impact of this to almost negligible levels, although even on my 8-core, 32-gig, SSD-based beast of desktop, the initial login does still take a few seconds longer before being usable than subsequent ones.
By the way, love the fact they changed the BSOD to an unhappy face. Like that's going to make me feel better.
Anyhow, I threw 8.1 preview on the build box and one thing I noticed - even if I change RAM it seems to throw it in a fit.
Most times so far it seems I've had to reinstall. Anyone else with similar experiences?
garwynn said:
By the way, love the fact they changed the BSOD to an unhappy face. Like that's going to make me feel better.
Anyhow, I threw 8.1 preview on the build box and one thing I noticed - even if I change RAM it seems to throw it in a fit.
Most times so far it seems I've had to reinstall. Anyone else with similar experiences?
Click to expand...
Click to collapse
Be aware that if you do a normal shutdown it hibernates the kernel instead of a shutdown (fast boot, saves RAM image to disk) so that will cause a BSOD so remember to do a cold boot or restart and pull the plug in the BIOS screen.
jessenic said:
Be aware that if you do a normal shutdown it hibernates the kernel instead of a shutdown (fast boot, saves RAM image to disk) so that will cause a BSOD so remember to do a cold boot or restart and pull the plug in the BIOS screen.
Click to expand...
Click to collapse
Now it makes sense! Wasn't aware of this, thanks!
Sent from my SPH-L900 using Tapatalk 4