[Motorola Droid RAZR] Ohmster:
Thanks for the update, 2¢./ Now the last time we discussed this slideshow crash, you were going to try a real MMS 3rd party app, not the built in SMS app, your words. So, how is that working out?

...not to be mean or a smart-ass. We covered this issue in post #6310, and concluded this may not be the fault of the built in My SMS app. The slideshow is an advanced MMS feature and iPhones have this capacity. I use Go SMS Pro and another one that should work is SMS MMS Messenger. I don't know for sure if it will solve your issue but then we can rule it out or be done with it. ;)

Wow, 10/21 is a huge update! Thanks to your tip, I am going for it. :)

EDIT:

Only had 10/21 in for a little while but the device seems to work quite well, seems smooth and fast. So far, so good. You know, this update seems extremely slick and responsive. I can't wait to see if it reduces the residual lag that seems to appear hours later or next day on my phone in 10/19.

---------- Post added at 02:01 AM ---------- Previous post was at 01:23 AM ----------

Oh duuuuude, this is awesome and just the kind of data I am trying to pull from the group. Most people with issues like this ignore them or don't feel it is important enough to complain about. These system snags are what I want to investigate. That's right, wiping dalvik/cache does clean it up, but not for very long. After several hours or overnight, it comes right back. Wiping isn't the answer. One tool I can suggest if you use Xposed Modules is CPUFreq in Statusbar. I love these system health reports but this is the only one I found that does not tax the system. It does not cull data nor build graphs, badges, charts, or create a UI to display cpu frequency. All it does is run a 1 second loop and print the contents of the current cpu frequency file, already on the system. Not a big job and it does not slow things down. You get a nice red 1200M, yellow 800M, or green 300M in your statusbar, once per second. Neat to watch, after booting, connecting, and syncing, your phone should show a nice green 300M idle freq in statusbar, should be 1 minute or less unless recovering from a full reboot.

For this CPU Freq module to be useful, you need to use a CPU Governor that will shoot up to full throttle to get tasks out of the way and then quickly drop down to idle frequency such as the ONDEMAND governor in /Settings/Performance/Processor. A performance governor never drops below 1200MHz.

Hey, when you get this lag, is it only present for the time it takes to switch data networks? So after you get locked in, 2-5 minutes, you are good to go, no lag to see dialer UI when calling or receiving a call? If you get or make a call during this extreme lag period, do you get a black screen w/status and navbar present and white spinning circle while waiting for the dialer UI to come up? This is pretty important so I can separate it from my own lag or see if it is the same, regardless of what sets it off.

Constant synching will for sure slow the device down. DumbleCore gets a super fast phone by eliminating ALL of it. Not for me but it proves a point. Trouble connecting or slow to connect to your cellular network is a possible choke point when you exit WiFi and switch to cellular data. See how long it takes to get online with cellular network by toggling airplane and watch for data lock, ideally w/out orange bars as that would be proof of data lock. If it takes several minutes then you might be in a weak signal area. What is your signal strength?

I just did a quick test with a digital timer. From rebooting to update Xposed framework when I could first see the signal icon appear (orange) to Google Server lock (No orange bars) took 1 minute 6 seconds. It took 2 minutes 11 seconds to reach an idle 300MHz in statusbar while the device continued to synch things like Facebook (I got a FB toast.) and finally drop to idle. Is that good or bad? I don't know but it

is a point of reference

.

I will think about this and help you sort out a way to test and dig for data. Not sure now, need time to think this out. But we now have a few suggestions on how to get started. And this is a bug I want to stamp out so we will work on this together, okay [MENTION=2895830]rgerrans[/MENTION]?

Anyone else see their phone choking or slowing down, even a little? You can help by reporting it, when it happens and how long the lag lasts. Thank you all very much. :highfive: