Jump to content

mikejeep

Honored Premier Sponsor
 View Profile  See their activity

  • Posts

    3,284

  • Joined

  • Last visited

  • Days Won

    197

 Content Type 

Everything posted by mikejeep

  1. mikejeep
    Sorry, didn't see this until now.. I have noticed that non-CDMA connections seem to update much slower than CDMA ones. I do testing with my N5 on T-Mobile and noticed it.. it doesn't appear to be the app, signal updates are just slower. No. But you can test out the beta one that should be available within a couple of hours.. -Mike
  2. mikejeep
    Interesting. My N5 definitely has never dropped back to send or receive, so it must be a limitation with Sprint or CDMA in general. I like not dropping back to 3G in fringe areas, but it's tricky because I know I'm not receiving any texts. I still get voicemail notifications, but I'm using Google Voice for that. -Mike
  3. mikejeep
    Oh in "regular" LTE mode it definitely does, messages are sent/received much faster than without LTE. But I was referring to LTE-only, where I suspected you have no eCSFB because you have no 1X fallback.. ..which confirms my suspicion. Thanks! -Mike
  4. mikejeep
    Man you guys are sweethearts this week, can someone please convince my wife that I'm this valuable? It's not directly related to all of your sucking up, but it's certainly not hurting either.. but a huge update is almost ready for testing. Pretty cool stuff.. some stubborn things are finally getting crossed off the to-do list. I think the "sticky" PLMN is resolved once and for all, 8T8R identification is working, neighbor cell display is slick, you can hide unavailable/disconnected connection types, and there are now log fields for strongest signal and its location. It still needs some finishing touches and testing on my end before it goes anywhere, but most of the work is done. I am still trying to figure out why Android L hates SignalCheck.. there won't be a fix in this update, but it's the next thing in the pipeline. -Mike
  5. mikejeep
    No, not really.. it's just phone calls. Any SMS delays I've noticed usually had a good reason. Although this might be a good time to ask this -- should SMS work when in LTE-only mode? I can't send or receive any messages when I do that. -Mike
  6. mikejeep
    I was specifically referring to missing calls while connected to LTE despite having a strong signal and in a known solid 3G area. -Mike
  7. mikejeep
    Aww, well I am totally humbled by that... I don't really know what to say... thanks Josh I'm always amazed when I see the stats. This past week it was installed by the 50,000th different user, and it's still installed on over 21,000 devices right now. I know it's a miniscule slice of the Android pie, but that is still unfathomable to me. I am flattered that so many others find my work to be useful. It makes all the effort worthwhile! Thank you to every single one of you -Mike
  8. mikejeep
    You can't view them directly in the app (yet), but you have two options: 1) Go to Logs > Export Log, that will export the entire log as a comma-separated text file. It will be saved in a folder named SignalCheck in your default storage location -- typically the SD card or other accessible folder on your device. The filename is the date/time of the export, so you can export as often as you like and old CSVs will not be erased. Exporting a log does not clear it. 2) You can access the raw sqlite database at /data/data/com.blueline.SignalCheck/databases/signalcheck_log.db. Most devices require root permissions to access this folder. I'm working on adding additional export options, import options, and viewing the data from within the app, but I can't say when any of that will be ready. I'm a slow learner -Mike
  9. mikejeep
    After suffering with this for awhile myself, the problem went away several weeks ago.. but suddenly started occasionally happening again this week. Hopefully it's just a sign of more upgrades and a temporary nuisance. Putting my N5 in 3G mode completely resolves the issue. Sprint just tells me to do a factory reset, so I'll just have to be patient. -Mike
  10. mikejeep
    It's coming to SignalCheck in an update very soon.. -Mike
  11. mikejeep
    On the Android issue tracker.. I don't think it necessarily matters, but if more people 'star' this suggestion, perhaps Google and the AOSP folks will take note: https://code.google.com/p/android/issues/detail?id=54947 -Mike
  12. mikejeep
    Ahh, I just looked at your report closer.. I see the LTE signal strength and cell information is completely missing. If you can get the beta version installed on there, keep an eye on the "C1" value on the diagnostic screen and see if that ever fluctuates with your signal. If so, I might be able to get a little bit of information working. But it does look like BBos isn't fully reporting signal data to the app. How does it work when you are not connected to LTE? -Mike
  13. mikejeep
    Sprint's coverage map seems to be corrected now, it shows the latest update as of today. One thing I have discovered about this map is that the LTE coverage isn't always as overstated as we think it is. If you zoom in enough to get the "Turbo/Best/Fair" ranges, it seems fairly accurate to me -- with one major caveat. You need to have your device in LTE-only mode to see these results. It seems as if their "fair" LTE areas should really be labeled "you will be kicked back to 3G here". Also, this is with my experience with a Nexus 5, a stellar RF performer. -Mike
  14. mikejeep
    I saw your diagnostic report -- it looked to be working, no? -Mike
  15. mikejeep
    As a developer, it drives me nuts as well. Would love to get a standard method to obtain frequency/band information, but it just doesn't exist. There is a suggestion in to have it added, but it's never been addressed. Seems like it should be a simple addition and it would be very useful for the apps a few of us on here have created. -Mike
  16. mikejeep
    I thought I already had you on my list? I don't need any more but I'd like to extend an invitation to you anyway. Will send you a PM. -Mike
  17. mikejeep
    I've actually been working on it quite a bit.. it looks like the odd/even route is reliable. I also may have fixed the "sticky" PLMN issue but I'm not positive about that. An update will be out for the beta crew this week with some good stuff in it! -Mike
  18. mikejeep
    Did you select the Excel timestamp option under Preferences > Logger Settings? Ugh the current version still does this? Thought I had that fixed.. I will take another look at it. -Mike
  19. mikejeep
    That depends on the state. In MA, drivers cannot "send or read any electronic messages" while driving. Hands free does not matter. It's not only about the hands on the wheel, but also about the distraction it causes. -Mike
  20. mikejeep
    The "sticky" B41 only happens if you connect to a Clearwire B41 site (PLMN 311490 or 311870), even if it's just for a moment. If you're definitely not, there could be a software issue with your device -- more likely a bug than anything actually broken. Try going to About > Send Diagnostics and send me a report next time you see the issue. Be sure to include your username and a brief description so I know what the report is for. It should help me pinpoint the issue. Also, a device reboot is not necessary if anything gets "stuck" -- resetting your mobile connection or exiting/restarting the app will do the trick. -Mike
  21. mikejeep
    I think it's important to realize that the N5 probably isn't getting "yanked" from anywhere.. they are just going out of stock and Google isn't manufacturing any more of them. -Mike
  22. mikejeep
    Wow.. I think I know who my favorite person of the week is! I just went through my log as well, and out of over 1,000 entries I have saved (Massachusetts, New Hampshire, Florida, Michigan, Minnesota, ATL, BWI, MKE, and ORD), every single B25/B26 site does have an even third character. And the handful of B41 sites (all Clearwire / pre-8T8R AFAIK) all have an odd character. I trust what you're saying, I don't need your log at the moment -- but can others check and confirm this? Particularly in other markets and where NV 2.0 deployments are live. I don't need specifics other than if this pattern holds true and where you are. -Mike
  23. mikejeep
    This is my all-time favorite phone. It's rare that I'm not chomping at the bit to grab the latest-and-greatest as soon as I'm eligible for a discounted upgrade.. I've been eligible since June and have no interest in anything else out there right now. We'll see what the Nexus 6 brings to the table, but I'm good for now. -Mike
  24. mikejeep
    Haha well I'm not a programmer either, that's the problem!! You are absolutely right though, and I've been leaning toward that solution because it would work much better. And the new 8T8R sites are apparently using 310120 so I need to do something like this anyway. The sticking PLMN is becoming more of an issue as B41 rolls out to more areas (everywhere but here it seems like). The problem is that doing this is not as easy as it is for B26.. at least not yet. For B26, the sector bits will always match a very short list. The B41 sectors vary quite a bit, and follow the same pattern as B25 in some areas, so that's out. Matching the beginning of the GCI (the market portion) will work, but I would have to collect all of the possibilities -- there are dozens, if not hundreds. But once I had that list, it would work better than the current setup. I'm looking into either building something within the app to submit logs to me to be parsed automatically, or creating a basic Google Doc for people to submit B41 GCI's. Ultimately I'd like to fix the PLMN problem anyway, because even if the band is displaying properly, the ID could still be wrong. And someday there will be LTE roaming to consider too. -Mike
  25. mikejeep
    It does look like the market ID +1 pattern might be consistent, but it is still early. If that's the case, it will pose a challenge to me because I would have to figure out all the possible B41 IDs and check against that list.. and hope Sprint didn't change anything down the road. I was really hoping that they would just follow the B26 pattern of changing the sector IDs.. that would make things very very easy on my end! If the middle (site ID) portion of the GCI turns out to have an offset that is consistent everywhere, I can work with that. If it varies by market/vendor, that's going to be tricky. No matter what, I agree that we need to see more evidence before calling anything a definite. -Mike
×
×
  • Create New...