Jump to content

Mosaik purchases Sensorly


lilotimz

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

I can remember back when Mosaik Solutions was formerly American Roamer.

 

AJ

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.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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