Jump to content

Why is RootMetrics app seem so inflated?


Duffman

Recommended Posts

.

 

This is more than twice what either the Speedtest or FCC app measured. Anyone know why?

 

I have talked with Kevin at RootMetrics about this in the past. RootMetrics uses the same servers for the most part that Speedtest does, but it searches out the best server it can locate before it starts running the test. It's doing that while it is running the signal portion of the test. When it settles on the best server, it then starts speed testing it.

 

I think RootMetrics is a more reliable speed tester in my opinion. The results are accurate. It is sending files to the remote server, and this is the speed actually observed in the transfer. If you were streaming video from that same server, it would be moving at the indicated speed in RootMetrics.

 

SpeedTest app (and the FCC app is also made by Ookla too) are a little too user dependent in choosing a server. Often, people are not using the best server. And they are just oblivious to it. Typically, people will choose the same server they use at home. Which is never a good idea, because wireless backhaul is likely routing its destination to the internet differently every time. And it will likely hit the internet a very long ways away from where their home and work ISP's do.

 

That's why I'm always recommending that people who use SpeedTest to use several different servers when they get a really slow speed result. With apps like SpeedTest, FCC, and even RootMetrics it's not the fast results that are suspect. It's the slow ones. It can't register faster than the connection it actually has to the server on the other end.

 

Every time I can think of where I had a fast RootMetrics speed, I was able to recreate it on SpeedTest if I kept hunting around on different servers...eventually.

 

Robert

Link to comment
Share on other sites

Another thing that provides a little validity to the accuracy are the Upload speeds. We know that Clearwire limits their WiMax upload speeds to 1.5Mbps. I can occasionally get it up to 1.6Mbps, but never 1.7Mbps. If that had said something like 2.0Mbps, or 2.5Mbps, then we know there was a significant problem with these results. Also, that EVDO upload speed also is not out of whack.

 

Robert

Link to comment
Share on other sites

I think RootMetrics is right on-- look at all their detailed reports market-by-market... excellent information that seems to agree with everything I've observed and heard from users in those markets. Opensignalmaps.com is another good unbiased user data sourced resource to use for research.

  • Like 1
Link to comment
Share on other sites

I reviewed all their reports before making my decision to jump to big red. I was on Sprint 10 years, so carrier moves are something I don't take lightly. I'm a little upset that Verizon didn't win 1st place in Dallas, but that is the one market they don't have cellular 850 in-- only PCS A block there... but at least they won every other market.

Link to comment
Share on other sites

Look at North Florida on the map' date=' and you can see what I have to deal with.[/quote']

 

I reviewed all their reports before making my decision to jump to big red. I was on Sprint 10 years' date=' so carrier moves are something I don't take lightly. I'm a little upset that Verizon didn't win 1st place in Dallas, but that is the one market they don't have cellular 850 in-- only PCS A block there... but at least they won every other market.[/quote']

 

And these posts are relevant how?

Link to comment
Share on other sites

So giving this app a try, I notice a lot of failed connections.

 

Is it just not good with crappy networks? Speedtest shows me my horrible sub 100 speeds fine in the same area, but seems rootmetrics just fails and wont post a speed until it hits 100+.

 

Just asking as I go back to painting my town red/black.

 

Sent from my PC36100 using Tapatalk 2

Link to comment
Share on other sites

So giving this app a try, I notice a lot of failed connections.

 

Is it just not good with crappy networks? Speedtest shows me my horrible sub 100 speeds fine in the same area, but seems rootmetrics just fails and wont post a speed until it hits 100+.

 

Just asking as I go back to painting my town red/black.

 

Sent from my PC36100 using Tapatalk 2

 

I do also get a lot of failures on RootMetrics in sub 100kbps speeds. It seems to be related to ping when that happens. It seems to me when I go over to SpeedTest app when that happens, the ping is over a second. In those instances where ping is normal, but speed is not, it seems the RootMetrics app is able to cope. That's my observation.

 

Robert

Link to comment
Share on other sites

didn't even think of seeing if it was ping related. That might be it for the download test.

 

Upload still fails 70% of the time for no reason that I can see. But I do really like the mapping rootmetrics does, so i'll keep plugging away at it.

 

 

 

Sent from my PC36100 using Tapatalk 2

Link to comment
Share on other sites

I would think that a large part of the routing difference between home and cell, other than routing itself being stochastic, is the fact that Sprint phones route through their proxy servers by default.

 

This looks pretty good if ideal speed is of interest, though.

 

Honest question: what is the interest in ideal speeds?

Link to comment
Share on other sites

My interest in speed checking is just to look for and note improvments.

 

Here during the day time your lucky to hit 150kbps. So I like looking at sprints network site, seeing which tower got a band aid fix and then retesting to see if it improved and by how much.

 

Sent from my PC36100 using Tapatalk 2

  • Like 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...