Performance loss after booting in safe mode once ?

[Darthy1980]

Hello,

I have a rather odd question. I had some battery isses right after I bought my HTC One last week (which seem to be caused by a wakelock "MSM_HSIC_HOST") and HTC asked me to boot the phone in safe mode and do a battery test. Battery test worked out fine and HTC told me this specific wakelock should be fixed in the update to Android 4.2.2 (fingers crossed).

However, I have the feeling that now the phone feels a bit slower after I had rebooted again to get out of safe mode. I had only used my phone for a day or 2 before so I could be imagining this, so hopefully you fellow One owners can put my mind at ease
I sometimes have some UI lag, but it's very, very minor, but it is there. For example when I have 10 tabs open in chrome and I close them in rapid succession not all of them will close without a very small framedrop. It just bugs me on such a new phone.

I've run a couple of benchmarks to compare the results with the results on Anandtech of the One (both GPU & CPU) and those all turn out great, right on par. I donno, maybe the safe mode boot activated some extra logging that's still active or something and slowing the phone down ? Although only thing I did was run the battery test.
I did a test yesterday with a friend who has a nexus 4. We both cold boot the phone, wait like 20 seconds for any background things to load and then both boot Google hangouts (which seems to be the slowest app on the planet right now ). His Nexus 4 was actually faster, but only by a very, very small amount. This test is of course not really conclusive as it might be an IO or memory speed limitation instead of CPU. Doing this takes my Hangouts around 4 seconds to load after a cold boot. What are your numbers for this ? Do you also notice some very minor UI lag sometimes ?

It just bugs me, phone is still very fast but I really have the feeling it was just a tiny bit faster before I had to do that battery test. Can someone put my mind at ease ?

Some extra info: battery saver mode was disabled in this test (but I have the UI lag both with it enabled and disabled, doesn't seem to affect the phone much if you enable battery saver mode except a lot of better battery life because of the reduced "MSM_HSIC_HOST" wakelock).

Thanks,

Jorn

 

[Gator352]

First off, try a factory reset. An app could have got borked somehow causing your phone to produce what your describing. OR you could use Gsam battery app to tell you which app is causing the wake-lock so you can eradicate the culprit.
,
About chrome: Chrome is NOT the most proficient browser in town. It's good, but not without it's faults. Having 10 tabs open uses a lot of memory to keep them active and wiping them all at once IS going to slow it down. It's going to do this in any browser you try. First, it has to clear your ram, then your tabs, then the app causing a little bit of "lag".

Also, how your phone performs is indicative on how much stuff you have running in the background, email, facebook, twitter, etc. If you have a lot running, it's going to slow down a little. To note, the nexus 4 is no slouch but it does run stock android. There is no launcher or carrier bloat to slow it down. That is why many prefer stock over anything else.

I have not heard of or experienced this particular wake-lock before and my One runs like a Ferrari right out of the factory BUT I do at times run into a little bit of stuttering now and then. Every phone on the market, including apple, experiences this.

Hope this helps ya!

 

[Darthy1980]

Hello,

Thanks for the reply ! The wakelock seems to be a common issue with the HTC One (but maybe not with all of them) and should be fixed with a kernel update in 4.2.2, so I'll wait for that (should be soon I hope ). If it doesn't fix that I'll try the factory reset. I did install Gsam also to keep an eye on it (was using BetterBatteryStats), so thanks for the tip.

The phone still feels very fast in 99% of the cases. I guess I was just expecting a little bit too much of the One (or any ARM based phone maybe) But if it's normal (it's by no means impacting the user experience too much) then my mind is at ease, thanks

Jorn