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

    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • Oct security update is out.
    • Stopped by again today and the antennas are up but it isn't live just yet. If other Sprint conversions are anything to go by it'll likely take about a month for the site to go live.
    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
  • Recently Browsing

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