Jump to content

Mosaik purchases Sensorly


lilotimz
 Share

Recommended Posts

I know very little about Mosaik. But it will be nice that Sensorly will now be run stateside.

 

Sent from my Nexus 5 using Tapatalk

  • Like 3
Link to comment
Share on other sites

Hopefully the become more responsive and further separate out their LTE to make it more accurate.

Link to comment
Share on other sites

Separate their LTE to make it more accurate it what way?

 

Since it is based on RSRP, the Sprint results can be rigged by only using B26.  By the same token B41 will be measured as much weaker.  The release notes in indicate attempts to address CA with certain phones.  Using my LG G4 I have yet to see any difference.

Link to comment
Share on other sites

It would also be nice to see them weight by how old the data is, or even put a filter that allows you to only show data collected in the last (whatever time interval).  Also giving stronger signals more weight, so it's not diluted by people mapping while indoors or with phones without every band.  Sprint results got diluted because so many people mapped so much when it was just B25, which makes the all-time aggregate signal strength appear weak almost everywhere.  I also don't like that it basically shows you "here's where at least one person ever got a signal, even if 99% of the time you can't get a signal here."  When multiple people map and fail to get LTE on a previously mapped area, it needs to count that against the fluke points and remove coverage from the map.  I think that's a big one: I don't like seeing so much purple on the map where I know no phone on any band can get a usable signal - you might as well use the carrier's own coverage maps at that point. 

 

Basically it's a great service for a casual viewer who wants to get a ballpark idea of coverage for carriers, but the way it was originally coded in many way makes it less accurate over time.  Under new ownership, and depending on how the data was originally collected, I'd love to see them implement a few changes that would make their maps much more accurate/valuable to consumers. 

  • Like 1
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.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Mine is still working fine here in Raleigh.   There were some outages related to the snow storm.    I have seen it take a couple of days to recover from storms.   It is not among the highest priority services.  
    • Looks like my MB gold at my office was finally decommissioned sometime last week. It was working the previous week and I was out of town last week. I came in today and it was powered down. I unplugged it and plugged it back in but it just keeps looping through trying to establish a connection. Looks like it's time to add it to our ewaste pile.
    • I did spot some NRCA in Crown Heights last weekend. Sadly because I'm using an iPhone I can't see the exact carrier combo but it did report that it was seeing 2 NR carriers. At first I thought it was a glitch or some weird stale data because my phone was still reporting NSA 5G and the primary NR carrier was the 80MHz n41 carrier but reading Sascha's article it's quite possible that my phone was using B2+B66 +n41+n41.  — — — — — On another note, it looks like someone found n5+n77+B2+B66 on Verizon:  Edit:  Two more confirmed locations of conversion sites:  T-Mobile eNB 875316 Location: 40.7314623618499, -73.82849493999701   T-Mobile eNB 875868 Location: 40.75304305996773, -73.85311593221213
    • This entire FAA argument is stupid with no evidence at all that there is an issue with C-band.  You may be right that there is some conspiracy nut involved. The guard-band between what aircraft altimeters use and cellular C-band is 220MHz.  If any safety critical aircraft altimeter is reading signals from 220MHz away from the frequencies it is designed to use, that is a very broken safety critical device and should have been replaced it long ago.  Everything in an aircraft is designed and certified for precision and is checked regularly.  The aircraft is not designated as airworthy for instrument flight if the systems in it are not certified to be precise and in good working order.  If an altimeter is so broken that it is off by more than 220MHz from the frequencies it is designed to use, it could just as easily be off by 1GHz or more which would likely cause it to fall into other frequencies that are also already in use. 
    • https://www.pcmag.com/news/exclusive-we-found-t-mobiles-secret-weapon-against-c-band Seems like he's seeing: B2+B66 +n41+n41 n71+n41 Not that it really matters, I suppose:  
  • Recently Browsing

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