Jump to content

mikejeep

Honored Premier Sponsor
 View Profile  See their activity

  • Posts

    3,269

  • Joined

  • Last visited

  • Days Won

    188

 Content Type 

Everything posted by mikejeep

  1. mikejeep
    I'm baaaaaaack! Are you still having these issues? If it's definitely happening in tandem with 800 sites, the only thing app-related I can think of would be 800 alerts. Have you tried disabling all of them? How about disabling the 1X geocoding? Do you notice the BID jumping around like crazy, or does it stay fairly steady? Does the BSL change rapidly? When you say it crashes play store, do you mean it says "Google Play Services" crashes? If you exit the app completely, does Google Play crash at all when you are in those areas? I know that's a lot of questions, sorry! -Mike
  2. mikejeep
    Boston has several incarnations of Washington Street, none of which are near each other. I-93 South is the same as I-95 North for awhile, and vice versa. But don't call it I-95 anyway, because it's really 128. Sort of. Street names almost always change when crossing into another town, regardless of how major the roadway is. I could go on for pages and pages.. -Mike
  3. mikejeep
    Wow.. that is clearly a dramatic difference.. and both look ridiculous to me. It works perfectly on the EVO LTE because that is my primary test device, and the code is optimized for that screen resolution. Devices with screen resolutions that are much bigger or smaller (like yours) than the EVO end up looking silly. Heading on vacation shortly, but I'll start improving that when I get back. -Mike
  4. mikejeep
    Missed this until now.. just wanted to throw my well wishes onto the pile, and say congrats! I sincerely appreciate the ridiculous amount of time and effort you put into this site. Don't worry about us, S4GRU will be in good hands.. family and real life is priority. Hope you can find a way to enjoy all of that traveling and moving! -Mike
  5. mikejeep
    I have not changed anything with the widget in the past several versions. It should always have been 1x1 but I know some devices show it differently. I don't think it has ever been resizable, at least not intentionally. Making the widget look better and more standard across devices (it looks perfect on my EVO) is on the list of things I want to do.. need to teach myself some new things to get that done though. -Mike
  6. mikejeep
    Reboot your device.. that's an Android bug. Sometimes the geocoding service crashes and only a device restart will resolve it. Take a peek at that FAQ page when you have a chance, each of the specific issues you have asked about are on there. We don't mind helping, but you could've started enjoying all the features of the app quicker. -Mike
  7. mikejeep
    Hmm.. I haven't heard of any Sprint sites broadcasting invalid BSL information, that's a Verizon thing. Some updated sites are broadcasting a more accurate location than before. I didn't see any mention of this in any of the Iowa threads. Do you have proper SID/NID/BID values? Feel free to post a screenshot. -Mike
  8. mikejeep
    Sounds more like something from the App Store's T&C, not the Play Store -Mike
  9. mikejeep
    A special announcement from your friendly neighborhood SignalCheck developer: I will be on vacation and without Internet access from Saturday 9/27 until Tuesday 10/8. I have intentionally not released any program updates in the last couple of weeks because I wanted to ensure a stable release was out while I'm away. There are some features in the pipeline that I have been working on and will push out to beta testers shortly after I return. If anyone has issues or questions, speak up now or wait until I get back.. if I come back.. -Mike
  10. mikejeep
    I thought it was weird to see a Verizon 1X connection with a BSL! Strange blend of information right there. Did you happen to check and see if your engineering screens were showing the same info? The SID/NID/BID are all essentially updated with the same command, so I assume your phone was confused at a lower level, it's probably not app-related. The BSL was probably still displaying because the app doesn't force a refresh unless the BID changes. Perhaps I should make that a little more broad, since technically you could switch SID and/or NID but hop onto an identical BID.. 1-in-32767 shot I guess? -Mike
  11. mikejeep
    Haha, not yet.. but once the technical details start coming out, I will get to work! I would love for a tri-band HTC One-ish device to come out, I would snap one up for myself and development purposes.. but it doesn't sound like there is anything like that on the horizon though. I have said this 100 times, but maybe the more I say it, the better the chances of it happening are: Hopefully the newer devices take advantage of the newer Android routines and don't require as much back-door hacking like many of the handsets out there now do. -Mike
  12. mikejeep
    I would tend to think its more of an issue with your device instead of false Sensorly data.. -Mike
  13. mikejeep
    The site(s) that other users were connecting to while mapping those LTE signals may not be online at the moment. Perhaps the site(s) were broadcasting temporarily while in testing, or they have gone offline for some other reason. Have you connected to LTE anywhere else with iOS 7? I don't see how/why the readings in that area would not have been valid user submissions. -Mike
  14. mikejeep
    Don't quit your day job. -Mike P.S. I know you must know the truth behind ASU.. you know everything.. spill it!
  15. mikejeep
    I have been trying to educate myself about "asu" as it relates to signal strength.. it appears that that GSM and LTE use different calculations for asu, and the few formulas I have found are consistent with each other. However, none of the sites I found were terribly reliable.. and SignalCheck is pulling far different values directly from some LTE devices. GSM data appears to be correct though. Here are the formulas that I am trying to confirm are accurate: GSM ASU = (RSSI + 113) / 2 [valid ASU is in the range of 0-31; 99 = unknown] LTE ASU = RSRP + 140 [valid ASU is in the range of 0-97; 99 = unknown] Now here are conflicting examples on LTE connections that I have seen recently: Samsung Galaxy Victory -93 dBm, 2 asu (status screen) [should be 47 asu?] **EDIT: Its showing the 1X RSSI. Huh. -116 dBm, 11 asu (SignalCheck) [should be 24 asu based on formula above?] Nexus 7 2013 -106 dBm, 34 asu (status screen) [appears correct?] -105 dBm, 17 asu (SignalCheck) [should be 35 asu?] EVO 4G LTE -108 dBm, 13 asu [should be 32 asu?] (SignalCheck) -112 dBm, 13 asu [should be 28 asu?] (SignalCheck) -117 dBm, 10 asu [should be 23 asu?] (SignalCheck) I am guessing that because GSM has been around longer than LTE, any bugs in those calculations have long since been ironed out, so there aren't any conflicts with those numbers. It looks like the SignalCheck LTE ASU values are roughly halved, perhaps as a result of a blend of the GSM equation with the LTE one. Hard to go with that theory until I can confirm that the equations I found are correct though. -Mike
  16. mikejeep
    http://www.cellmapper.net/ is another one. Even before I found S4GRU, I felt that Sensorly was the most popular service, and they had the best mobile app. OpenSignal has some strange things in their app (like the "which direction is your tower" estimator that I have never observed working with any accuracy) that make me scratch my head. -Mike
  17. mikejeep
    Hmm.. it sounds logical on the surface, but I'm not so sure that's the case. The alerts are just stored in Android as true/false values passed by the checkboxes on the preference screen; the options themselves do not have anything to do with sound or vibration. If sound profiles on the device were doing something to third-party app user preferences, that would be a bad thing. However, There is a component in the app which disables certain CDMA-only preferences if it thinks a GSM signal is present; perhaps some phones are triggering that. It wouldn't affect any LTE preferences, but it would disable anything related to 800 or 1X. I am changing and testing those routines now. -Mike
  18. mikejeep
    Weird! I have never seen this happen on my own EVO, but apparently it's a fairly widespread issue affecting several different devices. I will figure it out.. -Mike
  19. mikejeep
    Ahh you guys are killing me! Haha.. nah I do appreciate the reports, like you said, I don't know what's broken until someone reports it. I have a hunch as to what might be causing some options to become disabled. It probably only happens in certain phones.. looking into it, I'll keep you updated. -Mike
  20. mikejeep
    Hmm... that definitely should not be happening. Nobody else has reported that, but I might have figured out why it's doing it. PM me your e-mail address and I will send you a fix to test out. -Mike
  21. mikejeep
    I don't think so.. deck is a developer who works on HTC devices. Good point though, I wonder if there is any similar progress in CM on Samsung devices? -Mike
  22. mikejeep
    digiblur helped me out here, he was correct -- bold indicates that it's a "new" BSL -- one that has not previously been saved in the cache. It's on the 4.09 change log (http://www.bluelinepc.com/signalcheck/change-log/) but that's it.. maybe someday I will get around to putting reasonable documentation together, but for now the FAQ and change log will have to do -Mike
  23. mikejeep
    I talked to Fubie, but just so everyone else has a heads up -- the relevant code is already in all versions of SignalCheck; its not new or a beta feature. The GCI label was added recently, but its the exact same information that previously appeared in the app under "Serving Cell" or "CID". You will automatically see the GCI and/or PCI on *any* ROM that reports the information. lordsutch and other CM devs definitely seem to be leading the way on this.. thanks for all of your hard work guys! -Mike
  24. mikejeep
    I think it's funny that we are all interested in the G2 because it's the first tri-band phone.. yet if you go on Sprint's site, there is no mention of its tri-band capabilities whatsoever: http://www.sprint.com/landings/lg_g2/index.html?INTCID=CHP:RG:LG:20130903 -Mike
  25. mikejeep
    SignalCheck Lite 4.14L has been released on Google Play! It's a relatively minor update, includes all relevant features that Pro users received in 4.13, but without the bug I introduced and fixed in 4.14. See my earlier post for the changelog: http://s4gru.com/index.php?/topic/3060-signalcheck-android-app-to-monitor-your-2g3g4g-lte-signal-strengths/?p=199714 It seems like all of the bugs have been squashed (at least for the moment), so I'm working on adding some new features again.. stay tuned. -Mike
×
×
  • Create New...