Android 5.x Issues Gone After Wipe?

I recently procured a Samsung Galaxy S5 to replace my S3 and man was that an upgrade; it was fast as lightning compared to my clunky S3 that seemed to trip over itself.  The S5 came with version 4.x installed, so I ran updates to get everything ready.  I realized that after the upgrade to 5.0, the entire phone became insanely sluggish, as in worse than my S3.  I had read about this a bit prior to deciding on the S5*, so I looked up more on this and found the scenario to be true.

Terribly annoyed, I decided I would just perform a wipe and reset everything to factory default, crossing my fingers that I could revert to 4.4 by doing that.  As it turns out, a factory reset only wipes the user data and has no effect on the OS version.  If you want to do that, it’s a pretty intensive task that I would rather not have to deal with.  I decided to just go ahead and run with restoring my phone with everything I had backed up until I could plan out everything.

What I’ve found, however, is pretty crazy.  After performing the wipe and still having 5.1 installed as the OS, I’m finding that the phone is running better than before.  Keep in mind that I only had this phone for about 5 days before I performed the wipe, so it’s not like I had a year-old phone that had enough gunk installed all over the place.  Also keep in mind that I’ve only just got everything all set up how I like it again, so maybe this will all change after a few days.

Another thing that I’ve now noticed is that the battery seems to be operating at a normal level.  Before, the battery was being eaten up like a Gamorrean by a rancor.  Since the wipe after the upgrade, the battery lasts so much longers.

Regardless, I’m pretty shocked by this.  I don’t have a bunch of phones to test this on, but I’m wondering if after upgrading Android from 4.x to 5.0 you then wipe to factory defaults and then set up the phone with all apps and settings, does it run as it should?  Is there something wrong with how the upgrade process performs that would cause the OS to degrade?

If anyone out there can confirm this, that would be something worth sharing with the Android and Samsung community.

*I went for the S5 because I don’t need the latest and greatest phone out there.  I tend to get a model or two below the newest phones, mostly due to the crazy price difference between the two.

Advertisements

KB2926765 – Long Install, High CPU Usage

And yet again, it is my displeasure to announce that I have encountered another recently released Microsoft patch which has caused me distress due to an incredibly long install time on some systems.  The patch this time around is KB2926765.  Most of the servers that this was installed on ran it without too much of a problem, but there were definitely some delays.  Just as in one of my other posts, things come to a crawling halt.  Sometimes the CPU usage was maxed, while other times it was only around 15%; notably, VMs tended to have the hardest time with this patch.

As noted in the previous post, some of those who left comments stated that SEP was the culprit.  Once this unfortunate process began, I tried disabling SEP.  That didn’t seem to make much of an impact on the systems which were currently installing the patch.  On the systems which still did not yet have the install process initiated, I disabled SEP and the installs seemed to go through quicker.  I’m starting to think that I just need to disable SEP at the beginning of every server patching.  Eventually (and I mean 30-60 minutes), the patch does install.  You just have to be patient, even if it means that the cleaning crew has already come, gone and shut out the lights, leaving you in the only lit room and all of the AC shut off.

Good luck with this patch, and if you happen to have any insight, please leave a comment.  Your contributions last time resulted in dozens of happy people posting here to thank us.

EDIT: I’d also like to include that you may experience an error code 80240016, stating that updates have failed.  This is the general error code for another installation was running while your system attempted to install another update.  What I found was that even though Windows Update declared that the updates failed, a reboot and recheck for updates will show that the installations were actually successful.

Microsoft KB2868116 – Very Slow Install Process

With today being Patch Tuesday, it’s time to get cracking on those systems.  Everything seemed fine for the most part, but one patch (KB2868116) gave me some issues on a few servers.  The specific issue is that it took over 45 minutes to install for some reason.  I’m not sure why or what causes this, but it’s something to take note of.

One system was a virtual machine that hosted a yet-to-be-used SQL server.  The other major time-stalled server was the server with Hyper-V that hosted the virtual machine SQL server.  Neither should have taken this long.  No events were logged in the event viewer to suggest an issue.  The Task Manager didn’t show anything too obscene in terms of system resources, although TrustedInstaller.exe did hit 100MB at one point.

Regardless, if you are planning on installing KB2868116, just plan accordingly.  Given what I went through, I would recommend installing all of the other updates, rebooting, then trying to install KB2868116 so that the system can attempt the installation with the caches flushed.  I’m not saying this will have an effect, but it is worth giving a shot.

PROPOSED SOLUTION: Thanks to the many people who commented on this post, apparently the culprit is Symantec Endpoint Protection (SEP).  These users have stated that disabling SEP will allow update KB2868116 to install quickly.  While this is a very easy workaround for single instances, if you are deploying via WSUS, that’s a royal pain to deal with.  Should you be using WSUS, I would consider approving the update late on a Friday so that it will install over the weekend.  While the PC may still require a reboot, at least users won’t get stuck for almost an hour with a wicked slow computer.

EDIT: I’m not sure if this helped “unstick” the process or if it was just a coincidence, but on two servers where it took almost an hour to install said update, I tried to stop the installation by hitting the cancel or stop button.  About 5-10 minutes after doing that, the installation process stopped, but showed that 28686116 had installed.  After a reboot, I installed the remaining updates without a problem. Hitting cancel won’t help the process go along.  I akin it to waiting for a long time at a red light and then flashing your high beams thinking you made the lights change.