Jump to content

Recommended Posts

Posted

I've been using sensorly for a quite a bit, although I've noticed it doesn't overlap existing coverage if better coverage exists at a later date. For example, one tower on a road has been broadcasting LTE for a while. While the signal is strong near the tower, and a deep purple on the map, further down the road it is weaker and a lighter purple. Now, 4 months later, the other tower down the road a few miles is broadcasting LTE and the signal is much stronger because of that. So, if I re-map this area that had a faint purple, it still shows the faint purple on the map, and not the deep purple stronger signal it should be. Anyone else experience this?

  • Like 1
Posted

According to a post by the sensorly people in the sensorly thread, sensorly averages the overlapping data when it is put on the map. So in other words it will take a few times of mapping the overlapping data to bring the average up and darken the purple on the map.

  • Like 2
  • 4 weeks later...
Posted

I have a Sensorly question too. But more of an Android question.

 

What is the cheapest Sprint LTE Android device that will run Sensorly without issue?

Posted

I have a Sensorly question too. But more of an Android question.

 

What is the cheapest Sprint LTE Android device that will run Sensorly without issue?

 

The Viper, Mach, GNex or Victory can be purchased on EBay pretty darn cheaply. Just got to look around.

 

Robert

Posted

I do not suggest the GNex though. We have a member even with stock vanilla ROM on his GNex, polluting the maps so much he stopped mapping once he realized it and saw it. Basically it was marking the maps with dark purple no matter if the signal was weak or not.

  • Like 1
Posted

Thanks for the info. Is there any particular version of Android which will or won't run fully functional Sensorly? I saw several on eBay that have 2.3. Is that sufficient?

Posted

Thanks for the info. Is there any particular version of Android which will or won't run fully functional Sensorly? I saw several on eBay that have 2.3. Is that sufficient?

 

What kind of phone? Trying to think of an LTE phone that has 2.3 still and can't think of any but I could be wrong. How much are you wanting to spend and do you actually want a decent phone or just a low bottom line phone?

Posted

What kind of phone? Trying to think of an LTE phone that has 2.3 still and can't think of any but I could be wrong. How much are you wanting to spend and do you actually want a decent phone or just a low bottom line phone?

 

Just need a bottom of the barrel Android phone to do mapping with Sensorly and run Netmonitor/Debug/etc. I want to use iPhone as my primary device but Android to use Sensorly on. Would not like to spend more than $100 if I can help it.

 

Can the Viper, Victory, Mach etc be upgraded to a newer version of Android? Or is it best to leave them at 2.3?

Posted

The Victory is a solid little device. Best RF performer of any Sprint Android phone I've ever tested. Even better than the OG Photon.

 

Robert via LG Optimus G using Tapatalk

 

 

Posted

The Victory is a solid little device. Best RF performer of any Sprint Android phone I've ever tested. Even better than the OG Photon.

 

Robert via LG Optimus G using Tapatalk

So, when's that phone comparison article coming up? *poke*

 

For the record, my sister has reported a marked improvement in usability in fringe areas after switching from the Photon to the Galaxy S III

  • 3 months later...
Posted

Why does Sensorly register roaming as it was a Sprint signal?

 

It is deceiving for 3G maps, especially since the speed is limited to 1x when on Verizon and maybe others.

Posted

Why does Sensorly register roaming as it was a Sprint signal?

 

It is deceiving for 3G maps, especially since the speed is limited to 1x when on Verizon and maybe others.

 

It's not limited to 1X, that's only on residential accounts/PRLs.  

 

I did ask Sensorly the same thing and they stated it was to show people where their phone would work.  I think it inflates the actual true network coverage which really distracts from the purpose of Sensorly.  People today are still freaked out about seeing roaming on their phone.  One of my lines asked me this when we were in the city roaming on VZW, I told her to eat it up, they should have signal here.  

Posted

Dig, speaking of asking Sensorly (since you seem to have the dev's address), my Sensorly question is....where has he been?  Just curious basically since he doesn't show that he's been around in over a month now.

Posted

Dig, speaking of asking Sensorly (since you seem to have the dev's address), my Sensorly question is....where has he been?  Just curious basically since he doesn't show that he's been around in over a month now.

 

Not sure.  I do know he's been busy busy, not sure on what, maybe other tools for PCMagazine?  I try not to bother him too much and funnel support from here through to him.

Posted

It's not limited to 1X, that's only on residential accounts/PRLs.  

 

I did ask Sensorly the same thing and they stated it was to show people where their phone would work.  I think it inflates the actual true network coverage which really distracts from the purpose of Sensorly.  People today are still freaked out about seeing roaming on their phone.  One of my lines asked me this when we were in the city roaming on VZW, I told her to eat it up, they should have signal here.  

 

I asked them this two about a year ago, they told me that it doesn't report when roaming, I know this is incorrect though.

 

I think its very wrong of them to do this.

It its roaming, they should have a different colour to indicate so. I don't mean a slightly/almost the same shade of green like Sprint does on their site, which is almost as deceiving.

 

It should be something Green = Sprint coverage, Orange = Roaming coverage.

Posted

I like that Sensorly shows roaming coverage. I just think it should be a different color.

 

Robert from Note 2 using Tapatalk 4 Beta

 

 

  • Like 2

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

    • It took a couple of months but this site is finally back online.  I was certain that a decommission permit would come through one day since it was offline for over 3 months but I passed by it today and it was working again. — — — — — This site is also finally live. This was probably the longest I had ever seen a site take to go live once all hardware was installed, about 3 months. Hopefully the site in Long Island City doesn't take as long.
    • So while we wait for @RAvirani to fix the website, I was able to connect one of my phones to Verizon n77 on a site with an NCI that appears to be adjacent to an NCI that was already in my database. Specifically, the site I call Taylor Run has been observed with these NCIs on n77: 44EEE469A 44EEE46AA 44EEE46AB 44EEE46BA 44EEE46BB I separately connected to the site I call Fairlington on its beta sector on n77: 44EEE46DA 44EEE46DB I'm assuming alpha sector is 44EE46CA/B.  With this data, I learned two things: 1) They're clearly not tracking the LTE GCIs with the NR NCIs.  Taylor Run is 1B61Fxx, while Fairlington is 1B680xx, not sequential. 2) It's clear that they're not using three byte sectors.  They're not even using two byte sectors like LTE does.  It looks to be done in an oddball fashion like how Dish is doing things.  Best I can come up with is a site ID that's something like: (NCI-0x20)/(0x30) It's possible it's actually (NCI+0x10)/(0x30) but I'm not really sure.  I also haven't connected to anything outside my immediate area here to know if this is consistent with other regions.  Not entirely sure how to persuade a device to do so, my Dish phone just connects to n77 at random in lieu of going to no signal.  (No data passes.) My take is to "break" the site notes for Verizon NR the way it was done with Dish NR, so at least the notes don't get copied to inconsistent sites, as has happened when I connected to Fairlington (came up as "Taylor Run").  It seems that Verizon, AT&T, and Dish all need work on the NR side to make sure site notes work properly.  Frustrating that they didn't standardize that for NR the way they did for LTE.  T-Mobile and US Cellular (while it lasts) seem to have done it the way I would have done it.  The others, not so much. - Trip
    • I tried to access that forum but it says I need a password. Is it limit to certain contributors?    I was going to report that the website is broken. For days it's been saying unable to retrieve signal data then going to a 404 error.
    • Sorry, I forgot about it when I posted previously.  And then I was talking to chamb by e-mail and away from my computer and suggested posting here.  Moved the posts to the proper spot. - Trip
    • It is probably better to post topics related to the map in the dedicated thread to help keep things organized and secure. This thread is big enough as it is, just want to try help keep things on track!
  • Recently Browsing

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