Jump to content

mikejeep

Honored Premier Sponsor
  • Posts

    3,284
  • Joined

  • Last visited

  • Days Won

    197

Everything posted by mikejeep

  1. What if you're dealing with ALU? -Mike
  2. This is EXACTLY the same problem I have been having for about a month! I posted about it a few times in here. I tried dialer modification apps and many other things, nothing works. Only happens when on LTE. I have resorted to forcing the phone into 3G-only mode for the past few weeks, which is extremely frustrating but I need to be able to receive calls. Haven't had any time to call Sprint from another phone to see what they suggest. I agree with the CSFB guess.. another wrench in the mix is I live in a mature LTE market (Boston) that never had any noticeable CSFB issues. -Mike
  3. Google Play automatically blocks devices that don't have hardware it determines an app needs. It must be missing something that Google thinks is required. I can't override the block, but if you are rooted you can grab the APK off your phone and sideload it. Drop me an email if you can't do that. -Mike
  4. Well that is interesting! 311480 is Verizon, which is why you're seeing that. Moat likely there is something up with CM.. maybe they have the PLMN hardcoded to VZ for some reason. Can you send me a diagnostic report if you haven't already? I'm mobile and can't get to those on the phone. -Mike
  5. Caught my first glimpse of Band 41 today! I was on 495 in the Lowell/Tewksbury area. Since I was driving, I didn't have a chance to do anything with it besides confirm SignalCheck and my N5's engineering screens were correct. Only connected to one site and then was bumped back to B25 as I went out of range. Excited to finally see a live signal in the wild, hope it spreads quickly! -Mike
  6. Knock it off you two, I'm not going there! The one version I have now keeps me plenty busy. If someone steps up and volunteers to tackle my 5 remaining graduate classes, and convinces my work to cut my hours down from the 75/week I'm averaging this summer, maybe we can talk.. -Mike
  7. No, you're actually the first to mention it I think.. many have asked for an iPhone version though. At this point, I don't think I would pursue it.. I don't have time for the Android one On top of that, I would have to learn a new environment and get my hands on some more phones. If there was a way to just port the Android version to iPhone and WP, I'd do it in a heartbeat, but this type of app has some very-specific routines that can't just be copied over to other platforms. -Mike
  8. Check your location settings in your device's Settings menu -- not within SignalCheck itself. Make sure that the option to determine your location using mobile networks (it's usually separate from the GPS option) is enabled. -Mike
  9. I have seen this a couple of times on my N5; it's very strange. Definitely seems like the radio is "hyper" after a call sometimes, and the only thing I can think of is the crazy flow of data overwhelms the app. The black screen freeze also happens occasionally if you lose signal for an extended period of time and go into the app before reconnecting to the network. I do have both items on my list of issues to sort out, but until now I didn't know that anyone besides myself had noticed it. Make sure you have the mobile networks option enabled under Location Services in your device's Settings menu. Some devices require this. -Mike
  10. Ahhh it was working during testing, but now I am getting reports that it's not. Looking into it now, will hopefully have something figured out soon. L users please provide me with any logcat messages you might be able to grab.. -Mike
  11. A SignalCheck Pro update (4.251) is out this morning! It is not a major update, but makes some strides. Here is a very quick summary, will edit with more details later when I have time: * Added indicators for AT&T LTE bands 2, 4, 5, 17, and 17 DAS. * Added site notes to notification pulldown. (Pro) * Improved Android L compatibility; SignalCheck alerts are not yet available on this OS. (Pro) * Improved Sprint LTE band 26 display reliability. * Resolved force closes when GSM PLMN is invalid or missing. * Resolved force closes when Location Service is enabled or automatically restarted on some devices. (Pro) * Resolved force closes when Wi-Fi MAC address is invalid or missing. * Resolved issue where invalid LTE site notes could be entered before the LTE PLMN was identified. (Pro) * Resolved issue where location information would stop updating. (Pro) * Resolved issue with stale 1X site, provider, and BSL information displayed when connecting or after connection is lost. * Updated GSM provider database. * Disabled support for Android 2.2. Lite will receive its companion update in the near future. -Mike
  12. Just because it's slower, and Sprint calls it something else, doesn't make it right. If we are striving for technical correctness, then we need to accept the fact that 1X and EDGE are 3G technologies. I completely understand what you are saying, but you're basing that off of the marketing that "3G" meant "fast" back in the day. There's no arguing the difference in speeds between 1X and EV-DO, but that doesn't mean they aren't both 3G. That being said, I think 1X/3G/LTE are the most appropriate and commonly-understood brief indicators for each of these. "4G" is too generic considering there are many different flavors of wireless tagged with that these days, especially for non-CDMA folks who have the various HS*PA options. -Mike
  13. Hey, you have had more than one question buddy! Sprint has configured its network to indicate which sector you are connected to by using the last two characters of the GCI. Most sites have three sectors, pointed in three directions like a triangle. The direction that each sector points in may vary by market or even by site; I haven't observed it to be reliable enough to say "Sector 01 is always North", etc. Band 25 and Band 26 sites share the same GCI except for the sector bits, which are typically similar to 00/01/02 or 01/02/03 for B25, and 19/1A/1B for B26, with some slight variations. -Mike
  14. The Logger will not insert any location data if you do not have the Location Service enabled within the app. It is a separate option to allow users to conserve battery power as they see fit. The location accuracy will vary depending on your device's capabilities, which location services you have enabled on the device, and your location settings within SignalCheck. I do know that the app will report coordinates as accurate as 10 meters if you have all location features enabled and can acquire a GPS lock. It's the timezone offset for that entry. The actual date/time values are UTC/GMT. If I had the timestamps simply record the current local time, the log could get screwy if you cross timezones at any point while logging. It's smart database management. The only wireless protocol that includes any base station location information is 1xRTT. Nothing else -- LTE, EV-DO, HSPA, etc. -- has anything comparable. Since the information doesn't really exist, I have no plans to add it.. -Mike
  15. Thanks for the kind words, Kevin! You're actually the third person to suggest this in here over the past month.. I definitely think it's a great idea, I just need to make sure I can implement it without corrupting existing database files. I plan to add a "strongest signal" column to the log with linked latitude and longitude columns that pinpoint where the device was when that signal was seen. It's near the top of the list of things I'd like to get done soon. It's definitely doable, I just need to find the time to tackle it! -Mike
  16. I agree that 1X and EV-DO should show different icons, but please don't forget that none of us who hang around here at S4GRU should be classified as an "average Joe" when it comes to mobile phones. Average Joes have no clue what 1X means. Even if they did, they would still dislike Sprint when they saw it. We are wireless nerds. -Mike
  17. No, it is not either of those things.. in some markets, Sprint uses offset coordinates that are some distance away from the actual site, in the direction of the sector it covers. See the FAQ for more details: http://www.bluelinepc.com/signalcheck/help/#bslwrong -Mike
  18. Oh if I did it, that would be the route I took. I will do it once I exhausted all the other options; I'm only hesitant because several others who experienced the same problem said it didn't resolve it. That's a lot of hassle for something that hasn't been shown to work. Nope, I'm rooted but that's really about it. Since my N5 is my primary test device, I try to keep it simple so I know any bugs are related to the app and not something else I might have installed. I have other test devices that I don't use for anything else, but the N5 is awesome because I can temporarily throw in a AT&T or T-Mobile SIM and make sure it's behaving well on those providers too. Minimizes my hate mail after an update! -Mike
  19. I was trying to figure out what apps I updated/installed, but I hadn't done anything in the past couple of weeks except for SignalCheck. And I uninstalled it just in case.. didn't help. Probably, since it seems to be an issue with the stock dialer screen. But I'd prefer to stay on the stock ROM; I'm an AOSP fan and think it's the best testbed for my app. I just found a suggestion to ensure I'm on "Global" and not "LTE (recommended)".. I don't see how that would impact it, but I'm giving it a try. Odd that so many people have reported this problem on various forums, but there isn't a clear resolution. And odd that it affects a random subset of N5 users. -Mike
  20. Hey I appreciate everyone's ideas! Nothing has worked so far, trying to find a third-party dialer to see if that helps. The only step I haven't tried is a factory reset, but I've seen many others who tried that without resolving the issue, so I'd rather keep looking for alternatives. It is a very inconsistent problem -- I was able to answer several calls today, but a short time later, I couldn't, and after rebooting, I still can't. -Mike
  21. Yes, that would be the B41 gremlins.. there is something going on where SignalCheck does not always show the proper B41 PLMN on the screen. The reports of site notes (sometimes) appearing in the log properly make me think that the app might be seeing the proper PLMN at some point, but it's not always displayed. This is the main issue I have been working to resolve, but haven't gotten anywhere yet. SpenceSouth (the LTE Discovery guru) has been kind enough to give me some ideas that I am trying out. I didn't have anything resolved for the update that is in testing now, but hopefully I make some progress soon. It's driving me nuts, but part of the problem is that I don't have any B41 live in my area yet (come on, Sprint!) so it's hard to effectively test. I have seen the problem first-hand when I travel, so I know all of you aren't crazy.. at least not for this reason.. -Mike
  22. Hmm.. sounds like it's saving your note with one PLMN but displaying another, so you don't see it. Check your Site Log and see if you notice anything odd -- even if you have never used it, that's where the notes get stored. -Mike
  23. Must have just been a coincidence.. it only worked for a brief time, then went back to misbehaving. Is it possible to flash an alternative dialer? Having a phone that won't answer calls isn't very useful.. -Mike
  24. I checked out your report.. there are no errors, and everything appears to be fine except for the missing information you mentioned. Check your system Location settings for your device (not the app).. make sure you have "Mobile Networks" enabled at a minimum. Are you seeing a valid PLMN and GCI on the screen? Does it give you a message saying you can't add a note, or does it let you add one but it doesn't appear? -Mike
×
×
  • Create New...