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
    Ha.. well I have no reason to have the app show bogus data, and the readings are pulled directly from the radio. But if they aren't showing something favorable to him, I can see why he might not be a fan. Each connection/section in the app is independent of the others, so if your phone has a particular connection, the app should show any combination that may occur. I don't recall ever seeing EV-DO by itself; it would have to be an odd scenario for that to happen -- like all of the 1X carriers in an entire area being offline, but not EV-DO. I'm not educated enough on the details to guess if that is even technically possible or not. -Mike
  2. mikejeep
    My best guess is the disappearing information has something to do with Band 41 not being ready yet; there has been a lot of strange behavior when connecting to (or trying to connect to) these sites. I've implemented your suggestion to save the most recent LTE cell ID information and display it if Show Hidden Data is enabled. It will be in the next update unless it turns out to cause problems during testing. I believe I have finally resolved the SID display bug, so I'll be prepping an update soon. -Mike
  3. mikejeep
    I have already been considering this idea, but I was wondering if it would be popular. Sometimes I do like to see what isn't connected, if that makes sense. You probably noticed it when not on a CDMA connection.. I changed the GSM screen on this version, and it hides non-LTE connections when connected to LTE; I did that because it better represents the fact that those devices don't have the capability to sustain multiple connections at once like a lot of CDMA devices do. I will add your suggestion to the list, at a minimum I will put it in as an option. Trying to come up with the best way to implement it. -Mike
  4. mikejeep
    Yep, I discovered that stuff a few weeks ago, cool stuff! It actually isn't N5-specific but I doubt a lot of phones implement it yet. I have a hacked-together routine I tested when I stumbled across it, and I know at least the GCI stuff was accurate in my area. Coming soon to an app near you.... -Mike
  5. mikejeep
    Thank you, I got them! With "Show Hidden Data" enabled, are you seeing signal information steadily? The reports you sent me show reasonably strong LTE signals, however, the phone is reporting that it is not connected to a known mobile data network (that's why the top line of SignalCheck says "Connecting...". But the system icon shows LTE and even SignalCheck says a mobile data connection is active and transferring data, very strange! I'm wondering if Band 41 on the G2 doesn't properly "identify" itself to Android. Maybe that's part of the mythical Spark update that is supposed to be coming soon... -Mike
  6. mikejeep
    Thanks for the support! That error message isn't coming from SignalCheck, it's coming from your phone's software. Since you turned on the LTE radio, it looks like your phone is trying to connect, but the network isn't allowing you to authenticate. You will see similar errors if you try connecting with a device that is not activated. As someone in that thread suggested, perhaps nTelos isn't allowing LTE connections yet. -Mike
  7. mikejeep
    The display of "SID: xxxx" itself is not a bug; that is what I designed the app to show if it checks the database and does find a valid result. The bug is the app isn't checking the database when it should. I've narrowed it down, but my Nexus 5 has only experienced it once, so it's tricky. It was definitely introduced in 4.19. That's why I'm not updating SignalCheck Lite just yet, because it's on 4.18 and does not have this issue. -Mike
  8. mikejeep
    Thanks William and PythonFanTN -- well said. Merry Christmas and happy holidays to everyone!! Hope Santa puts some RSRP in the air inside your stocking.. -Mike
  9. mikejeep
    That app to toggle LTE mode that you are referring to is called LTE Discovery, the developer is a member here and there's a thread about it too. It's a great app, comes in handy if you are still in a market where LTE coverage is thin. I'm spoiled in a great LTE coverage area, so I don't need it Also, that Nexus 5 Field Test app just opens the same menus that the *#*#DATA#*#* and *#*#DEBUG#*#* dialer codes do. You still need your MSL in order to edit any LTE band settings. -Mike
  10. mikejeep
    At least someone around here pays more attention to their real job than S4GRU.. I know I don't.. -Mike
  11. mikejeep
    You most likely caught a very faint LTE Band 25 signal, and your G2 decided it was better off on the stronger eHRPD signal. Check your Engineering Screen like Mercurial1 suggested; check your band as well as the PLMN (or MCC-MNC) and let us know. -Mike
  12. mikejeep
    Thanks for the kind words! What you're describing doesn't sound right.. first I'm hearing of it, but perhaps it's Band 41-related. Next time you are on LTE but the app isn't showing anything, please go to the menu and hit About SignalCheck > Send Diagnostics. That will hopefully give me some insight into the issue. Keep your head down in those dangerous neighborhoods in the meantime! -Mike
  13. mikejeep
    The app is only supposed to refresh the 1X provider name when the SID changes (which would happen whenever you switched between SMR (800) and PCS (1900) on Sprint). This is because there is no need to waste battery/RAM/CPU resources to constantly query the SID database if the SID has not changed. Obviously, I have a glitch in the code somewhere, because the app appears to "forget" the 1X provider at some point along the way, but it is not re-querying the database. The "SID: xxxx" display is only supposed to appear when connected to a SID with no match in the database. I do have good(?) news on this.. my Nexus 5 experienced this problem tonight for the first time! I haven't been able to replicate it yet, but at least this proves it's not a device-specific problem. I'm temporarily adding a lot of extra logcat output to try catching what scenario is triggering this. I will keep you guys updated. Just to confirm -- nobody experienced this bug until version 4.19, correct? -Mike
  14. mikejeep
    That should be easy enough! Another easy add.. I like it. Fits nicely into my layout re-design that I'm trying to get working too. It took me a little while to grasp what you were getting at, but I see it now. It's similar to something I have been playing with, although I was thinking of doing all the naming/editing on the device, not basing it off an imported file.. interesting. I have a new layout in the works that I am trying to get working properly, which has been my priority this week. Hopefully I can get that to a usable state so it can start being tested, then I can slide in some really cool things I have been cooking up. I'm not spilling all of my secrets, but my goal is to make life easier for those of you who spend a lot of time hunting down and recording sites... -Mike
  15. mikejeep
    Sort of.. I keep getting told that they are trying to find the right person who can help me. Today's update was that they found this mythical employee, however he is not back in the office until January. I have a few other contacts pending, I'll keep you updated. I'm still sticking with my guess that your sites are configured wrong. I don't mind looking into issues.. the Note 2 is certainly still a popular device, and worst case scenario, I can add the old menu option back on there if we can't get it resolved. I might do that anyway. -Mike
  16. mikejeep
    In the latest version, I changed the shortcuts to go directly to the data or debug screens because I (thought) I figured out how to do that. That Samsung hidden menu has a lot of extras that someone could really mess their phone up with, and the intent of my app is to give quick access to the most useful screens. Shoot me a PM with your email address, I have some things for you to try. We will get it sorted out! Thanks, -Mike
  17. mikejeep
    I have the Nexus 5, and have been all over Eastern MA & Southern NH with it.. haven't connected to anything other than Band 25 (1900) LTE so far. No issues with the CSFB problem either. Awesome LTE reception with this phone. -Mike
  18. mikejeep
    That means that none of the methods programmed into SignalCheck were able to successfully launch your debug screen. Did the SignalCheck shortcut work before you upgraded? Does the Data shortcut work? I'm not very familiar with the Note 2, what is the dialer code to access the debug menu? -Mike
  19. mikejeep
    I think you're exempt as "Staff" -- my 311 pages are suddenly down to 4, which makes sense based on my new limit of 200. -Mike
  20. mikejeep
    Seidio is having one last holiday sale, today (12/16) only -- 15% off everything and free domestic shipping. Use code DEC2013 at checkout. Full information here: http://app.streamsend.com/s/1/QcWY/XBb83P4/cl5lf -Mike
  21. mikejeep
    Thanks for the suggestion Jeffrey. That's something I intend to include when I finally start taking advantage of the expanded notifications available in Android 4.1+. I might be able to squeeze them into the regular notification if I re-organize some things, but that might be tricky. Stay tuned.. -Mike
  22. mikejeep
    Root permissions have always been required to use the Reset feature in Android 4.2 and beyond, because Google removed developer access to control the radio in 4.2. An alternative method was implemented in SignalCheck last August, but a rooted device is required. The failure message you are seeing is new with the latest app update, version 4.19. Previous versions of SignalCheck were not displaying the error message (it was supposed to, but a bug was preventing it), but I assure you that it was failing. If your device is rooted, ensure that SuperSU (or whatever root app you use) is granting SignalCheck root access. Sometimes the SuperSU prompt does not appear, or users have it set to deny access automatically. If your device is not rooted, you will not be able to use this feature on a 4.2+ device unless Google changes the security policy in a future Android release. It is frustrating many developers, but the decision is outside of our control. -Mike
  23. mikejeep
    The Nexus 5 does NOT work on Verizon. They are apparently the only provider not allowing it on their network. -Mike
  24. mikejeep
    Deleted a couple, but 311 pages @ 50/page = 15,500 if I counted right! Just more evidence we all spend too much time on here -Mike
  25. mikejeep
    Thanks Robert! I just noticed that I have thousands of notifications saved.. 313 pages of them going back to March. I can't think of why anyone would need that archive, and I'm sure it's clogging up a database somewhere. I started deleting them page-by-page, but that was a bit tedious. -Mike
×
×
  • Create New...