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.
Related
First, I am straight vanilla on my EVO--stock ROM, no root, etc. But I have noticed a behavior pattern in Android that reminds me of Windows 95. I am not a heavy or light user, just standard. But I have noticed that after a month or so, the UI begins to get clunky or jerky or sporadic (put your own word here). But if I pull the battery for a complete restart, it runs as smooth as silk again for about another month, when I have to repeat the process.
This reminds me of the old days of Windows when even Microsoft recommended PC's and servers be periodically restarted to clean up memory issues.
You went a whole month without rebooting your phone??
I've noticed a little lag after a few days but I rarely go even that long without restarting for one reason or another. I always though periodically rebooting was just something that was good to do anyways.
That is pretty standard for smartphones. I restart mine every morning when I get out of bed.
the fact that you can go a full month without rebooting your smartphone says something I think.
Well, I haven't been tracking the interval on a calendar, but a month (plus or minus a week) seems about right. But I am astounded that this battery-pulling process is "common" knowledge or that anyone would would think that doing it every morning is an acceptable practice!! Seems that people that b*tch about wifi speeds and light leak would be putting a gun to their heads if they had to reboot every morning...LOL.
You are "stock" not "vanilla". The two are not interchangeable. Vanilla implies AOSP non-sense which is what you want if that ui is bogging you down. Try adw or launcher pro and that sense ui lag will be a thing of the past. A custom ROM like cm6, fresh, or baked snack will fix you right up.
Swyped on my EVO
I am pretty sure none of the people who answered pull the battery for a restart. It's as simple as getting a program (quickboot) from the market to do it or long press on the power button. That is not a hassle at all, and really, every smartphone should be rebboted from time to time. This phones are now mini computers and as such from time to time will need rebooting to keep things smooth.
+1, pulling the battery is not necessary to reboot. I don't know why Sprint would suggest that is any different than just rebooting..
whats the name of the App in the market that will reboot your phone for you at a specified time/date/interval?
I know its in the market (and requires root) but i cant remember the name
dmc971989 said:
whats the name of the App in the market that will reboot your phone for you at a specified time/date/interval?
I know its in the market (and requires root) but i cant remember the name
Click to expand...
Click to collapse
I saw the thread about someone asking if an app like that exists, I didn't think it had been made yet.
I can see how someone who is not rooted could go a month with out restarting there phone. I mean most of my restarts happen because i am flashing a new kernel or rom or some combination of the 2.
What others listed is true though almost all smart phones need a reboot from time to time. Even newer PCS with win 7 you should reboot now and then so this wasn't only windows 95.
Also as stated above you dont need to pull the battery just power down and power back on and you should be good to go.
I think having to reboot your phone is a ridiculous notion. Just because it has the functionality of a mini computer doesnt mean that shortcomings of computers should be forgiven...
I mean, hell, portable gaming systems are getting more and more popular, but no one says hey its okay for my ds to overheat because its becoming more like an xbox 360...
icantdrawanime said:
I think having to reboot your phone is a ridiculous notion. Just because it has the functionality of a mini computer doesnt mean that shortcomings of computers should be forgiven...
I mean, hell, portable gaming systems are getting more and more popular, but no one says hey its okay for my ds to overheat because its becoming more like an xbox 360...
Click to expand...
Click to collapse
hahahahaha...
good one
a power cycle is unavoidable, thats when your system cleans up and wipes whatever isnt needed like temp files and what not, even regular cellphones from time to time require a restart, all computers require restart, what im more interested in is how android handles memory fragmentation, in ubuntu, they recently released a kernal upgrade that allowed for ubuntu to handle huge file sizes but now requires defrag to be able to compensate for fragmentation caused by using such large files and i was told that android has some sort of 2gig limitation on the overall os and i believe apps have a 15mb write limit or something of that sort, would that be to try and avoid memory fragmentation??
icantdrawanime said:
I mean, hell, portable gaming systems are getting more and more popular, but no one says hey its okay for my ds to overheat because its becoming more like an xbox 360...
Click to expand...
Click to collapse
That's not a fair comparison at all. Overheating is something that can damage an electronic device. I've never heard of a phone getting damaged by rebooting it.
Hell, for all we know, the OP doesn't even need to reboot. Running a task kill might have been enough to fix his problems.
IDK about you guys, but my battery dies so often and quickly, I don't think I can go more than a day without it dying at least one...
Whats the big issue with restarting? Takes like 1 minute.
Well, okay, nothing really about space aliens and robots, but you're here reading, aren't you?
Lots of discussion about pro/con of the EXT4 filesystem, risks to data integrity without journaling (analogous to a transaction log for a database), the disappearance of the reboot option on Bonsai (and maybe other ROMs) because of this, blah blah blah this, blah blah that, and on and on and on.
There is another solution. You can still have the performance of EXT4, without journaling. With much lower risk to your data in case of the battery leaping out of the phone on a whim. And good ol' reboot can make a comeback too!
The nirvana is a linux command called 'sync'. Crusty old unix hacks like me will get a twinkle in their eye at the mention of this command.
sync does somesthing very straightforward and simple: It syncs the filesystems. Put another way, it flushes the in-ram buffers out to "disk", syncronizing the actual state of the filesytem with what is stored -- and stale -- in secondary storage (hard discs on the big boys, NVRAM/SD/whatever on phones).
I've been experimenting with this to see if I can improve data integrity while minimally impacting performance. Here's what I've done:
Using GScript Lite, created a simple Superuser script for rebooting that looks like,
sync
sync
sync
/sbin/reboot #Bonsai ROM
Why 3 syncs? Paranoid. Nothing more.
Optionally create a shortcut on the homescreen to invoke this script to easy one-button reboot. I did this a week ago, have been using this to reboot Bonsai 4.0.0 a gazillion (actually, a bazillion, but I'm rounding) times, and have had absolutely no problems at all. Seems to work.
Created a shell script that launches at boot, as superuser, that runs in an infinite loop waking up every 10 seconds to do a sync. No detectable impact on performance that I can see. This is what I'd expect, as there is never more than 10 seconds of filesystem activity sitting "dirty" in the cache, so the sync doesn't usually have much to do (most of the time, nothing).
What does all this mean? Well, it's sort of a "lazy" journaling, and much more efficient. There's still a higher risk of data corruption under uncontrolled loss of power than with journaling, but in my considered opinion its negligible with the usage model/patterns for this particular situation (a smartphone).
FWIW, before I implemented this method for reboot, I like others got FCs on apps randomly after using the 3-finger reboot, simply running reboot directly from a shell prompt, or back on Bonsai 3, using the power-button menu reboot command. With this sync approach, I have not had a single problem -- and I can reboot the phone again easily!
What this means for you
If you're enough of a hack to understand how to implement this stuff yourself, give it a shot (at your own risk!), and let us know how it works out.
For the rest of you, be patient... I'm putting together a package to make it simple to install all this (initially just for the Bonsai ROM, others to follow, maybe), and should have something to test in a day or two. If you're interested in being a tester, PM me. Looking for 10 people.
I'm interested in this as I have been wondering about no_journaling for some time. I think it would help to prove or disprove the theory that no_journaling is causing data corruption. PM sent.
This is very interesting. I'll be watching this - depending on the results, it may be a good option for future versions of SRF.
I think a mod should move this thread over into the Development forum, please?
This sounds interesting. So will this "lazy" journaling put the same or less wear on the nand chip vs journaling being enabled?
If it has the same or similar wear factor as no journaling, as well as no impact on performance. Then this mod is a no brainer IMO.
Does sync only cause a write operation for data that has changed, or simply rewrite the entire buffer to disk each time? I'm sure you can see where I'm going with this...
Sent from my SPH-D700 using XDA App
It's better than nothing, but it still doesn't address battery pulls or phone freezes. It just provides a more graceful shutdown IF you do a clean shutdown.
dwallersv said:
Using GScript Lite, created a simple Superuser script for rebooting that looks like,
sync
sync
sync
/sbin/reboot #Bonsai ROM
Click to expand...
Click to collapse
I tried this on my phone and so far, so good. I am using ACS Frozen Rom 1.1.0 with Twilight 1.1.0. When I downloaded the GScript lite, there was already a script for reboot, I just edited it to add the sync lines. I assume that the #Bonsai ROM is a comment and not needed, so that was omitted. I have rebooted about 10 times (I know...many, many less than a Gazillion) and have not had any issues.
Thank you!
epic4GEE said:
This sounds interesting. So will this "lazy" journaling put the same or less wear on the nand chip vs journaling being enabled?
If it has the same or similar wear factor as no journaling, as well as no impact on performance. Then this mod is a no brainer IMO.
Click to expand...
Click to collapse
In terms of the precise impact on storage, it is indistinguishable from not doing it at all. All this does if change the timing of the writes -- you control it, rather than waiting for the OS to decide to flush the filesystem buffers.
In the case of a reboot, this makes a ginormous difference, because anything in cache that hasn't been flushed is lost if the system doesn't sync before quitting back into the bootloader.
Sent from my mind using telepathitalk
styles420 said:
Does sync only cause a write operation for data that has changed, or simply rewrite the entire buffer to disk each time? I'm sure you can see where I'm going with this...
Click to expand...
Click to collapse
only dirty blocks.
sync should not cause anything to be written that wouldn't be eventually written anyway, when the kernel decides it is either idle enough to perform the deferred task, or cache "fullness" requires it to make room for newer data by flushing older stuff that hadn't been written yet.
Sent from my mind using telepathitalk
poit said:
It's better than nothing, but it still doesn't address battery pulls or phone freezes. It just provides a more graceful shutdown IF you do a clean shutdown.
Click to expand...
Click to collapse
True on the reboot mod.
On the monitor, though, it can make a big difference in the case of catastrophe. The FS cache is never more than 10 seconds out of sync with the underlying NV secondary storage. Depending on the usage model, this may be enough to reduce risk significantly.
The interval, of course, is configurable. The monitor could sync every second, reducing risk further. Given the speed of the processor in the 4G, and the low overhead hitting sync when there's nothing to flush, the overhead at a one sec interval may be trivial.
I haven't progressed far enough with this nascent idea to have characterized such questions. It's on the work order, though.
Also, my rough experimentation with this is all via shell scripting, which has a lot of unnecessary overhead. Coding this into an Android service, calling the linux sync(2) system call directly will be much more efficient.
Sent from my mind using telepathitalk
hotwired34 said:
I assume that the #Bonsai ROM is a comment and not needed, so that was omitted.
Click to expand...
Click to collapse
Yes, just a comment... across different ROMs I've found that devs mess around with the location, and linking, of the reboot command.
I have rebooted about 10 times (I know...many, many less than a Gazillion) and have not had any issues.
Thank you!
Click to expand...
Click to collapse
let us know when you get to a gazillion... our at least to a bazillion.
Oh, and anything with aliens or robots that comes up as well
Sent from my mind using telepathitalk
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.
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...
(Note: I know just enough about UNIX-likes and what load averages are to get myself in trouble. )
Partially out of sudden curiosity, and partially out of frustration with my newly-acquired Razr M's short battery life, I poked around the developer tools and found the process/load average overlay, and left it on before pocketing my phone. (Note: it's running stock; 98.30.1)
I checked on it periodically, and it didn't take long to notice some incredibly high load averages when powering on the screen. The attached screenshot is the most ridiculous I've noticed thus far; having averages of near 15 across the board is not uncommon, but I have seen far more ... normal averages from time to time (around 3 across the board, usually).
What really disturbs me about this is that I'll usually find these high loads when the phone has been left to idle for LONG periods of time. I tried clearing all the widgets off of my launcher and minimizing background processes, but to no avail. Just what on earth could be causing this?
Strife89 said:
(Note: I know just enough about UNIX-likes and what load averages are to get myself in trouble. )
Partially out of sudden curiosity, and partially out of frustration with my newly-acquired Razr M's short battery life, I poked around the developer tools and found the process/load average overlay, and left it on before pocketing my phone. (Note: it's running stock; 98.30.1)
I checked on it periodically, and it didn't take long to notice some incredibly high load averages when powering on the screen. The attached screenshot is the most ridiculous I've noticed thus far; having averages of near 15 across the board is not uncommon, but I have seen far more ... normal averages from time to time (around 3 across the board, usually).
What really disturbs me about this is that I'll usually find these high loads when the phone has been left to idle for LONG periods of time. I tried clearing all the widgets off of my launcher and minimizing background processes, but to no avail. Just what on earth could be causing this?
Click to expand...
Click to collapse
I think just vzw bloat!
Get on the dst debloated SS or unlocked rom in my signature links. Then you could restore one or the other & compare.
It could be a bad app.
Do a safe boot up. (But how safe are you with the stock bloat?)
Pwr off
Pwr on
At the first sight of the big m press & hold the vol down & stay on it to home.
aviwdoowks said:
I think just vzw bloat!
Get on the dst debloated SS or unlocked rom in my signature links.
Click to expand...
Click to collapse
Bootloader's locked, and I can't root. (Yet, hopefully.)
aviwdoowks said:
It could be a bad app.
Click to expand...
Click to collapse
I've been pretty picky about what I install on my phone (most apps are installed on my tablet first, for testing/fooling around with).
I've uninstalled some software nonetheless, and I've disabled most of the bundled software.
aviwdoowks said:
Do a safe boot up.
Pwr off
Pwr on
At the first sight of the big m press & hold the vol down & stay on it to home.
Click to expand...
Click to collapse
I'll do some comparisons between that and normal booting later, and see what happens.
Strife89 said:
did you say root?.
Click to expand...
Click to collapse
We have root!
See general forum!
aviwdoowks said:
We have root!
See general forum!
Click to expand...
Click to collapse
For 98.30.1? That's fresh news to me!
Brainless Android start-up, thinking it has infinite CPU power, when it only has four cores on an old tablet. Wedges the thing with load averages above 20 for a good 10 to 15 minutes until it calms back down to about 4 or fewer process waiting to run... The becomes responsive again at about 3. No apparent way short of uninstalling about every app to control processes launched at boot/reboot/wake, tailor apps so they don't launch background activities, etc.