Jump to content

Carrier Coverage app developers react quickly to outrage of rooted users


pyroscott

Recommended Posts

Carrier Coverage was officially released on 6 Feb with the following disclaimer about rooted users:

IMPORTANT NOTE about ROOTED DEVICES! Although you will still be able to use the app and website flawlessly and your information will be collected/stored into the Carrier Coverage database, we will NOT be using rooted device information in terms of data reporting. There are too many variables and unknowns to accurately include this information at this time. I know many of you will be disappointed about this, but without accurate data, it totally compromises the potential accuracy - and therefore integrity of this project. And having reliable data needs to be priority #1.

 

By 7 Feb, after a rash of 1 star ratings by rooted users, they have already added

“** ATTENTION ROOTED USERS ** We will be updating the app THIS WEEK to offer support for rooted devices.” to the app description.

 

My thoughts, when I first read about the app, were that it could be an excellent tool to get an accurate depiction of coverage and not the estimation that the carriers provide. Once I set out to download and use the app, I was slightly disappointed that it excluded rooted users. It seemed counterintuitive that they would exclude the rooted users, as they are, in my opinion, the most likely to use the app heavily. Apparently rooted users are so excited about using this app, they are willing to spend the time to leave negative feedback. It sure worked, as Carrier Coverage was quick to react and start working on an update to include rooted users. I hope this minor mistake of not including rooted users from launch doesn’t discourage people from using the app and helping them collect data.

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

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

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