Recently I updated my device but It took 23 minutes to boot (First Boot) !! It was 12:21 AM and It finished booting at 12:44 AM !! Is it normal or there's something wrong ??
I suggest full wipe ...
Sent from my Transformer TF101 using xda premium
It's normal, it's rebuilding the Davlik cache. The more content and apps you have installed, the longer it will take.
It's a once only thing (at least until the OS changes, and then it may rebuild it again)
Yeah it's normal it happened to me the first time i put revolver on. Trust me I was freaking out
That's why it is recommended to always have full charge or AC adapter connected. Writing flash uses battery.
Thanks for sharing. I would've force rebooted it. Now I now I shouldn't!
Sent from my Nexus S using Tapatalk
this is my most hated thing about the EeePad - even if it's not the first boot, it takes ages. I hope CM9 and/or the ICS update fixes it.
unfnknblvbl said:
this is my most hated thing about the EeePad - even if it's not the first boot, it takes ages. I hope CM9 and/or the ICS update fixes it.
Click to expand...
Click to collapse
It's an Android thing, and unlikely to change. It's compiling and optimizing apps so they launch quicker. Without it, things will be very pedestrian.
unfnknblvbl said:
this is my most hated thing about the EeePad - even if it's not the first boot, it takes ages. I hope CM9 and/or the ICS update fixes it.
Click to expand...
Click to collapse
Still much faster than a simple? itunes update.
CrazyPeter said:
It's an Android thing, and unlikely to change. It's compiling and optimizing apps so they launch quicker. Without it, things will be very pedestrian.
Click to expand...
Click to collapse
Yeah, but it does it on every reboot. My eeePad takes about 5 minutes to boot even if it's not the first boot. We used to have this problem back in the days of Android 1.x, but the CM team managed to find a workaround for CM7. Some manufacturers have included a similar workaround (HTC's 'quick boot' function on the Sensation comes to mind), but obviously not Asus. Hence my hope that CM9 and/or the Asus 4.0 update fix things
unfnknblvbl said:
Yeah, but it does it on every reboot. My eeePad takes about 5 minutes to boot even if it's not the first boot. We used to have this problem back in the days of Android 1.x, but the CM team managed to find a workaround for CM7. Some manufacturers have included a similar workaround (HTC's 'quick boot' function on the Sensation comes to mind), but obviously not Asus. Hence my hope that CM9 and/or the Asus 4.0 update fix things
Click to expand...
Click to collapse
Then something is not right.
After a ROM install, mine takes about 10 minutes or so to boot, but it's once only. After than, it's int he region of 10 - 15 seconds from a cold boot to a working desktop.
CrazyPeter said:
Then something is not right.
After a ROM install, mine takes about 10 minutes or so to boot, but it's once only. After than, it's int he region of 10 - 15 seconds from a cold boot to a working desktop.
Click to expand...
Click to collapse
10 - 15 seconds, I'd love to see that, I get about 1 - 2 minutes average boot time rooted running revolver.
Sent from my SAMSUNG-SGH-I997 using XDA App
mine takes about 20 seconds to boot from off to desktop
I use Android Revolution HD 2.3.0
theraffman said:
10 - 15 seconds, I'd love to see that, I get about 1 - 2 minutes average boot time rooted running revolver.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Mine is stock but rooted.
And it's 20 seconds at the most from off to desktop.
To the person that said its an android thing- completely false. Zip aligned, number of apps etc. All factor. My transformer (rooted with latest revolver) boots within minutes if not seconds. After installing my backup of 100+ apps is when I get over 8 minutes.
Sent from my Transformer TF101 using Tapatalk
My Average boot time is 10 minutes....
theraffman said:
10 - 15 seconds, I'd love to see that, I get about 1 - 2 minutes average boot time rooted running revolver.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
I do not believe anybody's TF101 tablet starts up in 10-15 seconds. It's not even close to being ready to start at that point on stock, unrooted Honeycomb 3.2 firmware. Just tested my own tablet, which is close to as lightly-loaded on startup as you can get:
Slightly less than one second from the backlight turning on to the Asus logo appearing
Nine seconds from the backlight turning on to the "loading" circle animation appearing
77 seconds from the backlight turning on to the desktop appearing
90 seconds from the backlight turning on to my desktop widget being started up (ie. battery indication appears)
My desktop uses ADWLauncher EX, and has only one screen, one widget (TF battery widget), and the stock Asus (non-live) wallpaper. There is literally nothing else on the desktop, not even a single app icon.
My tablet has the following running at startup (bold are non-stock items):
* Lookout (2 processes, 1 service)
* Facebook (1 process, 1 service)
* TF battery widget (1 process, 1 service)
* com.asus.keyboard (1 process, 1 service)
* DMClient (1 process, 1 service)
* Google Services (1 process, 3 services)
* Maps (1 process, 1 service)
* MyNet (1 process, 2 services)
* Android keyboard (1 process, 1 service)
To those claiming their tablet boots in twenty seconds on stock firmware, I'm sorry, but I don't believe you. Post a video if you want to change my mind. My tablet couldn't start in twenty seconds (or even anything close to it), stock and straight out of the box without a single application installed.
Mine takes about 1 min on rooted stock 8.6.6.19
I *think* it is now longer than before, probably due to the amount of apps and widgets installed compared to before (although I try to keep as least as possible)
I have video to prove it, but I think it's a pretty normal time.
Will wipe and try revolver soon though!
Edit: it's a B70 SBK2
Sent from my Transformer TF101 using Tapatalk
knoxploration said:
I do not believe anybody's TF101 tablet starts up in 10-15 seconds. It's not even close to being ready to start at that point on stock, unrooted Honeycomb 3.2 firmware. Just tested my own tablet, which is close to as lightly-loaded on startup as you can get:
Slightly less than one second from the backlight turning on to the Asus logo appearing
Nine seconds from the backlight turning on to the "loading" circle animation appearing
77 seconds from the backlight turning on to the desktop appearing
90 seconds from the backlight turning on to my desktop widget being started up (ie. battery indication appears)
My desktop uses ADWLauncher EX, and has only one screen, one widget (TF battery widget), and the stock Asus (non-live) wallpaper. There is literally nothing else on the desktop, not even a single app icon.
My tablet has the following running at startup (bold are non-stock items):
* Lookout (2 processes, 1 service)
* Facebook (1 process, 1 service)
* TF battery widget (1 process, 1 service)
* com.asus.keyboard (1 process, 1 service)
* DMClient (1 process, 1 service)
* Google Services (1 process, 3 services)
* Maps (1 process, 1 service)
* MyNet (1 process, 2 services)
* Android keyboard (1 process, 1 service)
To those claiming their tablet boots in twenty seconds on stock firmware, I'm sorry, but I don't believe you. Post a video if you want to change my mind. My tablet couldn't start in twenty seconds (or even anything close to it), stock and straight out of the box without a single application installed.
Click to expand...
Click to collapse
Yeah, agree with you, mine takes about 1 min to show the desktop from cold boot and even from start with stock and no apps it took about this time.
fliparsenal said:
To the person that said its an android thing- completely false. Zip aligned, number of apps etc. All factor. My transformer (rooted with latest revolver) boots within minutes if not seconds. After installing my backup of 100+ apps is when I get over 8 minutes.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
so 3:30 - 4:00 minutes boot time with 200+ user apps is normal?
Related
I picked my Nexus S up this am as the store opened at 9am. I powered it on and away it went it had all of my apps dl in minutes.I had to go into work so I just let it charge on my car charger. Got to work and went to start Cardio trainer ( which is an app I use daily for about 3-5 hours per day) it immediately force closed. Force closes each time I try and use it. So i sent message to dev. The next thing I know I get a message saying that Beautiful Widgets geolocation is getting false reading from the GPS and it force closes. The GPS has been spotty. When first initiated it took over 10 minutes to get a lock. Turned it off and tried again and it took 7 minutes. The third time it was about 15 seconds and since then it alternates back and forth from almost instant to minutes again. What concerns me is that the accuracy just bounces back and forth from 32.6 ft to 16.3 ft and anywhere in between and really never stabilizes. This may be normal for this type GPS systems(I don't know) Also I have the old market and cannot find a link for the new market.Wasn't Gingerbread suppose to come with the new market? So far I am impressed with the smoothness of the system but not with the GPS. Also the lInpack scores are lower than on the Vibrant. Appears to be very solid. Anyone else have any of these problems?
tenbeau said:
I picked my Nexus S up this am as the store opened at 9am. I powered it on and away it went it had all of my apps dl in minutes.I had to go into work so I just let it charge on my car charger. Got to work and went to start Cardio trainer ( which is an app I use daily for about 3-5 hours per day) it immediately force closed. Force closes each time I try and use it. So i sent message to dev. The next thing I know I get a message saying that Beautiful Widgets geolocation is getting false reading from the GPS and it force closes. The GPS has been spotty. When first initiated it took over 10 minutes to get a lock. Turned it off and tried again and it took 7 minutes. The third time it was about 15 seconds and since then it alternates back and forth from almost instant to minutes again. What concerns me is that the accuracy just bounces back and forth from 32.6 ft to 16.3 ft and anywhere in between and really never stabilizes. This may be normal for this type GPS systems(I don't know) Also I have the old market and cannot find a link for the new market.Wasn't Gingerbread suppose to come with the new market? So far I am impressed with the smoothness of the system but not with the GPS. Also the lInpack scores are lower than on the Vibrant. Appears to be very solid. Anyone else have any of these problems?
Click to expand...
Click to collapse
It sounds like a GPS problem with your device, Just get it swapped mate
JD
I've only had FCs using the new google maps so far.
Random FC for me in maps, market and gallery :-/
ive yet to experience a FC
Cardio trainer is not working for me either, I am wondering if the dev's need to update it for 2.3, I also can't get vlingo to work.
JupiterDroid said:
It sounds like a GPS problem with your device, Just get it swapped mate
JD
Click to expand...
Click to collapse
I don't think it's a gps thing, I can't even get into cardio without it FC, my GPS locks without a problem.
phone randomly goes to boot animation screen
Ok, so it appears something is wrong with my phone. Every once in a while, i'll look down on my phone or in the middle of doing something, and it will go to the boot animation screen. Most of the time, the boot animation screen is dimmer than on normal start up. It will eventually go back to the ui, which I will then have to restart my phone because it won't connect to wifi or 3g.
Anyone else had this problem? Think it's worthy of getting a replacement from bestbuy or a glitch that should be fixed with an ota?
I haven't seen anything like this yet, though I suppose I don't keep my eye on my phone constantly, so I suppose it could have happened while I wasn't looking. No WiFi or 3G problems, either.
Sounds like you've got a serious issue there if you're seeing it a lot, though. I would get it replaced. Unless you're running a third-party ROM or some other non-stock mod, in which case dump it first and see if the problem is being caused by that.
Yea I had this happen twice. At gym was changing a track with Bluetooth headphones and went to dimmer bootscreen had to pull battery. And another time I had to reapply all my Widgets on my homescreen. I'm on CM7 rom
Sent from my Nexus S using XDA App
Are you using a custom ROM/kernel/SetCPU? Those problems sound like the ones the D1 has when it's clocked past a stable speed.
Sent from my Nexus S using XDA App
rocketragz said:
Ok, so it appears something is wrong with my phone. Every once in a while, i'll look down on my phone or in the middle of doing something, and it will go to the boot animation screen. Most of the time, the boot animation screen is dimmer than on normal start up. It will eventually go back to the ui, which I will then have to restart my phone because it won't connect to wifi or 3g.
Anyone else had this problem? Think it's worthy of getting a replacement from bestbuy or a glitch that should be fixed with an ota?
Click to expand...
Click to collapse
I'd look at the software you've added since the phone was purchased as the first primary suspect. Weird widgets, background services, live wallpapers, background syncing app, something like that...
You'd want to wipe/reset the phone before a return anyways, so why not do a factory wipe/reset from the settings/privacy menu, then start off with a fresh phone (software wise)? Be conservative in what apps you install at first, and check for stability; then slowly add back the stuff you'd have one by one and see which app from the Market causes the glitch.
I think that's a bit more fair to Samsung, Best Buy, and whoever ends up with the device as a refurb, than returning what is probably not bad hardware to the store.
demo23019 said:
Yea I had this happen twice. At gym was changing a track with Bluetooth headphones and went to dimmer bootscreen had to pull battery. And another time I had to reapply all my Widgets on my homescreen. I'm on CM7 rom
Click to expand...
Click to collapse
Hmmm...and you don't think the fact that you're using ALPHA level firmware that is known to have some bugs in it, might be your problem?
I'd expect that kind of thing with CM as long as it's alpha, and even beta. I wouldn't be surprised with it even on the RC versions. It's experimental until Team Douche releases an actual ready-for-prime-time version.
Are you using a custom ROM/kernel/SetCPU?
Click to expand...
Click to collapse
Nope, I'm not even rooted. I am however running ADW ex launcher. As far as widgets, the only widget i have running is the weather/news that came stock on the phone. As far as apps, I really don't have anything crazy downloaded or running.
rocketragz said:
Nope, I'm not even rooted. I am however running ADW ex launcher. As far as widgets, the only widget i have running is the weather/news that came stock on the phone. As far as apps, I really don't have anything crazy downloaded or running.
Click to expand...
Click to collapse
I've been running ADW.Launcher without problems up to now. I just upgraded to ADWLauncher EX last night; I'll post here again if I start seeing this issue.
this is similar to the other topic.
Random Reboots, we call it on the SGS (samsung galaxy s) side
hoping for the best, it is not the same deadly problem we found on some of the 16GB SGS phones, that eventually lead to the corruption / destruction of the internal SD
but those were the signs.
so i'm really hoping that is not the same problem, else i'll really be pissed with Samsung to produce yet another crappy phone with cheap internal parts.
it should not be, as i saw pictures of the innards of the SNS (samsung nexus s) and it was clearly showing SandDisk for the 16GB internal SD
Random Reboots
A couple of times I've had the Nexus S reboot, once when I was in the middle of a call and once again as I was messing around with the settings.
I'm running 2.3.1, th latest build GRH78, does anyone have an idea as to why the random reboots are occurring?
Thanks in advance for your help
Sent from my Nexus S using XDA App
Let's please keep it friendly and on topic here. Thank you
reception bar is stable but on active call it gets disconnected and i have to turn the phone off and on right away thia happens pretty often. I called samsung and they have no solution but to tell to go get it exchanged. This is already a second device.
Sent from my Nexus S using XDA App
Same thing happens to me.. now 4 times its happened to me
Sent from my Nexus S using XDA App
With the understanding that RC2 will be superseded by RLS1 very very shortly, I thought I would share my godmode "upgrade" experience from yesterday anyway:
For me, the elapsed time between booting into Amon Ra and finally getting a booted OS (let's define that as the earliest you can pull up the lock ring and get to a homsecreen, even if it is very laggy still) :
20 minutes grand total.
The total time before I could launch an app or actually use the phone in a meaningful way was more like 30 minutes.
Total time before the pain of initial lagginess no longer called attention to itself (ie, you could use the phone without the thought of "damn this is slow" intruding in your mind) : hours.
The long delays during the install process happen at times that are different from what I expected
Flashing the actual zip while in Amon Ra:
8 minutes total. Progress bar seems to hang on around the 50% mark (right under the "u" in Virus") for at least half the time, then the bar fills in to 100% suddenly, then a long wait at 100%, then back to the interactive Amon Ra interface.
At this point Rosie 3.0 carousel "non-landscape" people such as myself flash the appropriate mod ( I did the one with Rosie 3.0 widgets). Very brief ( a few seconds to navigate to your zip, a few seconds to flash).
What happens after you select "Reboot now" in Amon Ra?
First, the "white screen with black 'htc EVO 4G' text" (Note this is different from the "white screen with green 'htc' logo" you get later (and indeed any time Sense reloads, whether due to crashes, first boot, reloading after titanium activity etc)).
This lasted only 3 minutes.
Then the glowing green "SYNEAGY AOM" ( <-- not a typo, look carefully at boot animation ;> ) throbbing-synapse-loop boot animation.
This lasted 9 minutes. Sometimes the synapses throbbed very slowly.
Then finally a brief glimpse of lock ring on top of wallpaper. No shortcut icons visible. If you don't touch phone, the screen promptly goes to sleep. Which is fine. It could probably use a little quiet time at this point.
(If you just touch the power button but don't actually mess with lock ring it's amusing to watch what time it is. First it will be something like UTC time, totally off from your local time unless you're actually in England. Then a while later it will spontaneously change to local time, except in 24-hour format (eg 21:57) . Then finally it will revert to 12-hour format (eg 9:57). Takes several minutes.)
Finally I unlocked it and the first thing I was greeted with was a modal dialog saying "Process com.android.phone is not responding...Force Close / Wait". I chose wait and immediately was shown the "white screen with green 'htc' logo" for a good five minutes of totally non-interactive wait time.
I left the phone alone during this time and eventually it finished doing what it was doing and it fell back asleep. When I woke it up, I was placed directly in the Setup Wizard app. Interestingly, the first screen of the setup wizard has a 'back' button. Not feeling like signing in to anything just yet I hit 'back'. Again came the "white screen with green 'htc' logo", then a desktop with a dialog just saying "Loading" for yet another minute.
At last a real homsecreen appears (now with the familiar constellation of six icons, and, again, no clock/weather widget), the tips widget throws up a balloon with its first tip, and finally you can actually use the phone.
This would be around the 30 minute point since the flashing process started.
There are times during this initial break-in stage where it seems the phone is almost unresponsive. Touches may *begin* to get responded to after a five second lag or more. The response itself can take 5 seconds more to do something simple like simply redrawing a button with its highlight color after a button press, let alone performing the requested action.
That phone / wait dialog comes up a lot. For instance I just saw it again today when someone actually called me. I chose wait and then answered the call normally.)
Ominously, I also saw a dialog later concerning "android.process.media" which concerns me because the point of god mode is to change the way the filesystem works for basic I/O functions.
Still haven't ever signed in to my main google account yet. Seeing how far I can take this before I do. I suspect as soon as I sign in it will start downloading all my apps from the Market. Which force closed on me by the way when I was doing something totally unrelated (just poking around Spare Parts I believe it was).
Also the first time I tried all this the internet browser app simply did not work right out of the box. Force closed every time. (I restored app+data for just the browser app from my titanium backup I made (while running RC2 non god mode) prior to the install and got my browser back. That didn't give me warm and fuzzy feelings.)
Later I repeated the entire install procedure from scratch and did not experience market FC's or internet browser FC's. Not sure why the second time would be different.
Note I was not connected to AC power during any flashing or initial boot up.
For those playing along at home, you may be curious to know things like what kind of phone do I have, how did I prepare to flash, and what was the exact sequence of steps during wiping / flashing?
OG Evo HW 004, original SD card ( I believe that means 8 GB class 2), never toyed with any kind of partitioning. Previous ROMS have all worked fine with the SD card which has the usual folders full of pictures, nandroids, titanium, folders created by previous ROMs including Synergy, etc.
Latest radios, PRI, PRL, GPS works, 4G keys happy, never had any drama.
Before flashing God Mode I was already running Synergy RC2, and once I was ready to say good bye, I did a nandroid backup, then rebooted, connected to a PC and offloaded any new camera pictures, some recent nandroids and uploaded the ROM image ( I did check the md5) and the Rosie mod I intended to use (dkdude, not fdb) . Then ran titanium, backing up all user plus system apps, then finally did one last quadrant test (just under 1000), took a deep breath, and rebooted into Amon Ra 2.3 .
From there I did these wipes in this order:
rotation
battery
dalvik
cache
data
factory reset
Yes I realize many of these are redundant. Then, to be *really* redundant, I left wipe mode and went into flash zip mode and flashed calkulins format all tool. I believe this also wipes boot amongst other things.
So now at this stage the phone is fairly re-virginized. The only thing I haven't touched is the SD card which has the zips I want to flash.
Now I flash the actual synergy RC2 god mode zip (as described at the very top), then the rosie mod, getting no errors for either one, and then without further ado selected reboot now, which brings us back to the firstboot behavior chronicled above.
Edit: I did restore quadrant and got 1600 on my first run: make of that what you will.
[Reserved for updates on 4G experience, bluetooth, gapps, general usability etc...]
Quick update: I did successfully test 4G, WiFi, bluetooth, and GPS.
I finally signed in to Google and sure enough market downloaded all my apps. This may be a Synergy thing- Synergy also seems to remember things from previous installs despite the elaborate wiping regime described above, such as the password to my WiFi access point some search term history, maybe a few other settings.
Anyways, during the download and install of a moderately small number of market apps (I have like 15, all free) the phone was effectively unusable. Almost unresponsive. Finally a half hour after the install activity was no longer apparent, things seemed to settle down and the phone gradually seemed to become normal again.
Quadrant scores were originally as low as 1200 something. Then got it up in the 1400's, then finally i have seen several in a row in the mid-1500's. Again, for reference, I consistently got around 1000 with vanilla RC2 (and the same hardware gave me 1200 with CyanogenMod 7.1 RC1 for you AOSP fans out there).
And this is supposed to be an upgrade???
The party line is *once the phone has had time to settle in* things get a little faster in real world experience. I am in fact beginning to see the promised behavior now, 12 hours after install (including maybe 4 hours of heavy usage)
Certainly the improvements to the benchmark scores are immediate, but we can all agree actual 'driveability' is more important.
So far, I will say it's looking better with each passing hour.
As an example, the simple spinning carousel action (remember I'm doing the Rosie 3.0 carousel mod) under RC2-non-GM was clearly straining the limits of what the Evo could smoothly render. With god mode, it's clearly different, faster and smoother.
Here's the feeling I get: every time you do something for the *first time*, let's say the first time you launch a particular app, activate a certain part of the Rosie UI, get a new dialog box, there's a punishing lag. The *next time* you launch that app, or swipe that tab, or experience that same condition, it's faster. Indeed perhaps faster than it ever was in plain old RC2.
But the make-or-break thing will always be stability, or should I say predictability: days from now, if I still see a lot of Force Close's, or if I am still experiencing unexpected moments of slowness while it "learns" how to do something (and you know how Murphy's law works- it will always happen at just that moment where you can't afford to be surprised by a mysterious delay) - well, it may be back to regular Synergy. Hard to say. I'm a patient person. I intend to give this a good long audition.
When I Flashed the Alpha it took forever, but yes RC2+ was a very pleasant flash by comparison, just flash ROM - flash mount zip - flash carousel + widgets - flash unmount zip. then Im using link2sd and TB. Does anyone know of another a2sd gui that is good? want to prepare for RLS1
I had a similar experience giving rc2+ a try. It was borderline useless on my phone for whatever reasons. Went from rc2 to + after a nandroid backup and did a wipe of dalvik and cache. After about 6 hours of usage I said screw it and restored back to my nandroid backup which is blisteringly fast. The "seat test" on the phone wasn't great at all but the quadrant resulted in test results in the 1700-1800 range which is awesome. I too am on the stock class 2 card and I planned on buying a new card so maybe the results will be better with a new card?
TruthAEE said:
When I Flashed the Alpha it took forever, but yes RC2+ was a very pleasant flash by comparison, just flash ROM - flash mount zip - flash carousel + widgets - flash unmount zip. then Im using link2sd and TB. Does anyone know of another a2sd gui that is good? want to prepare for RLS1
Click to expand...
Click to collapse
The main Synergy thread is full of discussions on a2sd stuff.
Interesting that you flashed the rosie mod using the mount / unmount strategy. I chose to use a rosie mod that had specifically been re-written for godmode. I suppose you end up at the same place either way.
I wonder how it would run on a 32gb class 10.
Sent from my locked tight OG EVO using XDA Premium App
I have seen a lot of wildy varying reports on upgrading your SD card. When it works, it works. It's awesome. But there are also reports of even "class 10" cards that did not improve performance at all. Could come down to who the SD card manufacturer is.
If you tweak everything just right (note most people say to leave dalvik in internal memory regardless) with a swap partitioin, ext3 paritition, a2sd, then maybe one of the new custom kernels that have just come out, and maybe even apply the v6 super charger memory management trick, I bet this ROM could fly, benchmark or no benchmark.
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'm having many many days with this tablet that are frustrating.... Today for instance, I have had 2 re-boots and 3 hangs!!! My Xoom on a custom JB ROM didn't have these issues....!!!
I can't recall for sure, but I think I had maybe 2 total random reboots, and no app FC's (on stock ROM). I use CM 10.1's nightlies now and haven't had any crashes or hangs.
espionage724 said:
I can't recall for sure, but I think I had maybe 2 total random reboots, and no app FC's (on stock ROM). I use CM 10.1's nightlies now and haven't had any crashes or hangs.
Click to expand...
Click to collapse
is everything functional on cm10?
to the op, I have had the n10 hang while in chrome. when that happens, I have to reboot by holding down the power button until it kills power and reboots. on average probably once a few days. I am not a heavy user though. have tried dolphin browser and it too crashes although can't remember if it will hang the entire device.
Ever since I updated from stock, it runs hot and now getting reboots.
Never had an issues once and ran cool on stock rom.
Mines rebooted maybe 2 or 3 times total. Been using it about 4 hours every day for the past month. Hasn't been anything anywhere near what I'd call an issue. Running stock.
On a good day 1. On a bad day 4.
I turned off location services and stopped using chrome and have only had 1 random reboot in the last 2 weeks. Hopefully google fixes something soon.
None.
If I use chrome, its very likely that mine will crash. Using other browsers makes it less frequent. Hopefully they fix it asap.
I use my tablet for around 2-3 hours on work days and around 6 hours on days off. Today is a day off, and I've already had to force reboot it 3 times... I'm close to asking for a replacement, but I'm also going to try a few things before I do. There is no doubt about it. It should just work and it isn't. But before I send it back I will wipe and start over ( I am not doing any thing special with this device either. Everything is stock)
Most of the system hang's I get are almost always in Chrome. Sometimes Facebook or Twitter, and then when I have to force the reboot (pwr + vol up + vol down) it almost always reboots into installing a new app update... Which makes me wonder if that is the issue. I have disabled auto updating of apps, and have already had the same issue so I'm not convinced it was that after all.
So I guess I can either assume that my hardware is good and this is a software issue which I can wait for Google/Samsung to address or cut my losses and try and get a replacement device before X-mas... Right now the poll shows that more people are having a good experience than bad....
Thanks for the responses guys/gals..
Several a day with location services off.
It may hang up about 1 time per day. happened when portrate, almost.
I had a few at first i think it was due to the chrome browser on 4.2.1 but did a FDR and seems to be smooth now..
Also used the toolkit to root and works like a charm now
Haven't had any in CM10.1 but I had 1-2 a day with stock
Same here running aokp with ktoonz kernel. It's been more than a week without freeze/reboots. I don't game either tho & do use Ocean.
Sent from my Nexus 7 using Tapatalk 2
Depends on use. With heavy use every 3-4 hours? Its only rebooted once overnight. Mine seems more prone to do it while installing apps if I try to do something else while installing....although it will just as readily hang browsing with chrome. I was thinking of RMA but read some horror stories on that
Oh yea, Stock
Sent from my Nexus 4 using Tapatalk 2
dalingrin said:
Haven't had any in CM10.1 but I had 1-2 a day with stock
Click to expand...
Click to collapse
This. CM10.1 FTW. :good:
I was getting somewhere around 1-3 per day on stock. I've given up waiting for Google to fix it, so am now on cyanogenmod nightlies, and have not had one single freeze or reboot since. This tablet is now perfect.
Oops just had one more
Sent from my Nexus 10 using Tapatalk HD
My experience is virtually the same as Pihrana. I am under the impression that the hangs and reboots are a software problem that is likely caused by my particular usage patterns or an app or setting (I have location settings disabled and it still hangs). Either way I have decided not to exchange it, as the problem will very likely be addressed in a future patch, and I might end up with a device with hardware problems (light bleed, etc) in addition to the existing software issues.
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...