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
    I'm not sure; it is not unreasonable to think that Samsung uses a lot of similar internal code on radios for different devices, but nobody has reported anything to me yet. The dead giveaway will be if SignalCheck reports PLMN 310120 and the enginerring screen shows something different. I am also not sure how other flavors of the S5 (Verizon, AT&T, etc.) are affected. B26 relies on the PLMN being 310120, and since that's what is always shown, it works. Unless B41 sites start popping up with GCIs that end in 0F/1A/1B, etc.. -Mike
  2. mikejeep
    I received diagnostics from some of you, thanks. I didn't realize you all had an S4T, S5, or G2. Unfortunately, some of it is out of my hands. SignalCheck always relies on the PLMN to determine the provider, and also Sprint LTE band 41. There are several different Android methods to retrieve the PLMN, and SignalCheck uses the most reliable one. The S4T and S5 suffer from the same issue; both always report the "home" PLMN (in Sprint's case, 310120) to Android, no matter what it is actually connected to. The Samsung enginerring screens may be correct, but that's not what the system is reporting. This bug has existed since the S4T was released, but I was hoping the KitKat update fixed it, since they did address the missing LTE data. Until a baseband update comes out for these phones, SignalCheck will not show any B41 indicators. I have sent another note to Samsung about it. The G2 issue is odd.. it's also an issue with the system software, but as Vince reported, it's only wrong some of the time. I might be able to implement a workaround specific to the G2 that makes it more reliable. Thanks, -Mike
  3. mikejeep
    If possible, could you both e-mail your actual log databases to support@bluelinepc.com -- just want to start by making sure it's the actual log and not an issue with the CSV export. The database can be found at /data/data/com.blueline.signalcheck/databases/signalcheck_log.db; you may need to be rooted or grab it from a PC connection. Thanks, -Mike
  4. mikejeep
    Unfortunately, third-party apps don't have access to the data that the Enginerring screens do.. believe me, I've tried. A lot. You shouldn't need the BSL to save log entries.. can you email me any logcat errors or send me a diagnostic report? It should show me whatever error messages might be getting generated behind the scenes. Glad the updates fixed the instability issues for you! I plan to add a feature to import/export the database file in the very near future. It does appear that you need to be rooted to have full access to the databases folder. Did you completely exit SignalCheck before trying to copy it over? The app may have the file locked. Otherwise, you may need root access even if you are doing it from a computer. As I mentioned above, I plan to add more import/export options very soon. -Mike
  5. mikejeep
    Could each of you guys send a diagnostic report from within the app (About > Send Diagnostics) next time you believe you are on B26 or B41 and the app doesn't show it? Please be sure to include your username in the report and mention why you are sending it. Thanks, -Mike
  6. mikejeep
    "Searching for Service" while connected to LTE means you are in LTE-only mode. You can use data, but will not receive any telephone calls. It happens when you explicitly put your radio in LTE-only mode, or connect to a site with CSFB issues. -Mike
  7. mikejeep
    Yes. The LTE routines will now only indicate B26 if one of the previously confirmed band 26 GCI suffixes is present. -Mike
  8. mikejeep
    A new version of SignalCheck Pro (4.243) was released a few hours ago and should be already available on Google Play. This is a minor release that fixes bugs that popped up in the last update and have been discussed here recently, including: Improved reliability of LTE site note database entries. (Pro) Resolved force closes when certain Site Hint options are enabled. (Pro) Resolved force closes when enabling Location Service on some devices. (Pro) Resolved force closes when Location Service is enabled in locales that use a comma as a decimal separator. (Pro) Resolved issue with existing GSM site notes failing to be pre-filled in popup window. (Pro) Resolved issue with LTE site note display not updating on some HTC devices. (Pro) Resolved issue with no information showing when in EV-DO only mode. Resolved issue with Sprint LTE band 41 display missing. Resolved issue with Sprint users in Shentel and former US Cellular service areas seeing false indications of LTE band 26. Let me know if any issues pop up! -Mike
  9. mikejeep
    Are you stock, or on a custom ROM? Next time you connect to LTE and don't see information, go to About > Send Diagnostics; it will send me some useful information. There is a new app update that went out overnight that does include some fixes for HTC LTE functions, so that might resolve it also. -Mike
  10. mikejeep
    Thanks guys. As Sprint's new LTE rollout continues, there will be some bumps in the road while SignalCheck tries to keep up with the changes. I rely on reports from users to stay on top of this stuff. The version in testing now handles these situations better; both the Shentel and USCC examples will appear as B25. I expect it to be pushed out to everyone within the next 24 hours. -Mike
  11. mikejeep
    It has to do with your particular device or ROM. The commands that get the CDMA site information (SID/NID/BID/BSL coordinates) are classified as location features on some devices, even though there really aren't any location services like GPS or triangulation being used in the traditional sense. Therefore, if you have location services disabled in your device's Settings, the app will not be able to get this information. There are many phones that do not tie these commands to location services, and there does not appear to be any rhyme or reason why some devices require it and others don't. The app shows no connection(s) because it does not think you are connected to a CDMA site, since the routines don't return any valid information. LTE connections are not affected by this because the commands that gather LTE information are never tied to location services. -Mike
  12. mikejeep
    I'm not completely opposed to either idea, and will consider them in the future. It's a bit more complicated than you think, because it's not a simple as displaying a field that contains band information. There is no method within Android that reports any band/frequency information, the app identifies things like 1X 800 and LTE bands 26 and 41 by using information it can obtain and making an "educated guess" about it. So it's quite a mess of code in the background, and changes like this require a lot more work than you would guess -- small changes break many things at once -Mike
  13. mikejeep
    If anything, it would be the other way around. LTE puts the phone in CDMA/LTE mode. Global puts the phone in CDMA/GSM/LTE mode. That's it. -Mike
  14. mikejeep
    I'm confused.. you went into the store to ask about the Spark update for the Nexus 5, and not only did they show you their e-mail, but they gave you a free Galaxy Tab as well? -Mike
  15. mikejeep
    Sorry, haven't started any work on that yet -- it's on the list, but I've been focusing most of my efforts on stability/accuracy improvements, with the logging and site notes coming along as a side effect of that work. Once the crash reports stop flooding in, and B26/B41 is behaving the way it should, I'll be able to get back to working on extras like that. Not exactly sure what you saying here; is the app showing B41 wrong 18% of the time, or are you saying that 18% of band 41 sites in that area are actually on PLMN 310120? Someone mentioned that in this thread the other day, but never answered me. I went back through my messages and couldn't find any discussions you and I had about it, so feel free to PM/email if you have information. AFAIK, band 41 is only appearing on 311490 and 311870. Keep in mind that some phones have bugs that report invalid PLMNs.. last I heard, the Samsung Galaxy S4T reports 310120 all the time, and some other Samsungs report 31000 or 310000. Samsung may have already released baseband updates to fix these issues, I'm not sure. (EDIT: More info on PLMNs and Samsung enginerring bugs here: http://s4gru.com/index.php?/topic/5342-plmns-mcc-mncs-310-120-311-870-etc/?p=270791) As soon as I'm confident that the app is identifying B26 (and B41) accurately enough, I'll be adding those options.. I want them myself -Mike
  16. mikejeep
    You stole the words out of my mouth.. I hate that Sprint has no coverage (not only LTE.. they just don't have any sites at all) north of Concord except along 93 and in downtown Laconia, and has no plans to expand. I can't believe the complete lack if coverage around Winnipesaukee while the Big Two and USCC have it fully blanketed. I don't blame Sprint for not wanting to pay to expand into a seasonal vacation area that isn't likely to significantly boost their subscriber base, but the limited 1X we can access certainly doesn't convince anyone to not consider alternatives. Providing a reasonable roaming option would be fantastic. There are plenty of Sprint customers from MA and Southern NH that are up there regularly. I don't need unlimited 10mb/s, just provide something usable for light internet use and not sucking my battery down while it works its tail off looking for signal that isn't there. -Mike
  17. mikejeep
    Android does not update the CDMA site information while a call is in progress, so the app hides it on purpose.. the FAQ entry since it sums it up well: The 1xRTT SID/NID/BID/BSL values do not update while on a telephone call. This is a documented bug in Android. SignalCheck will hide these values while a call is active to prevent inaccurate data from being displayed. SignalCheck will not adjust the Sprint 1X 800 status during a call, which, in certain circumstances, may cause this status to be inaccurate until the call is terminated. -Mike
  18. mikejeep
    Nah, I think I figured it out.. when I fixed some issues with LTE-only mode in the last update, it broke EVDO-only mode. Thanks! Actually that was part of the provider name, "Sprint*" (subtle hint you were probably on spark.. get it.. ha). I greatly improved the reliability of it, so I confidently changed it to "Sprint B41" to be more clear. But there is a bug preventing it from showing up in the main app screen; it might show up in the notification pulldown. Both of these issues--along with all of the other bugs that popped up in the last version--have been addressed and one more round of beta testing will start this afternoon. A public update should be out within a couple of days, just need to make sure all the fixes really work. -Mike
  19. mikejeep
    I just tried it on my N5 and it seems to work fine. Weird. It worked fine for at least a minute or so, and then went to No Connection, despite a valid connection. I'll have to do some more troubleshooting. -Mike
  20. mikejeep
    A quick note to everyone.. The instant popularity of the new "site note" feature in SignalCheck has been awesome, but it has led me to think of something I hadn't considered until now. Please keep the S4GRU rules in mind when posting app screenshots here or elsewhere. Do not share information that is restricted to Sponsors or Premier Sponsors anywhere outside of those secure areas. The rules are very clear in each of those sections. Edit/blur/crop any proprietary information that you might have saved in your site notes before sharing screen shots. I cannot even imagine how much work Robert has put into this site, not to mention his support of my efforts. He is the founding member of my beta crew, way back in September 2012! I will not tolerate SignalCheck having ANY negative impact on this site whatsoever. It's great to see the new features being used so much, just please remember to respect the rules. That's all -- thanks for listening and I appreciate everyone's support! -Mike
  21. mikejeep
    Well the PLMN for bands 25 and 26 are identical, so nothing would happen there.. and band 41 uses at least two IDs. So it's probably just easier the way I'm doing it now. The complications arise from the failure of every Android device to report the PLMN in the exact same manner, so I have to use a few methods.. and don't forget, most of us are Sprint users, but the app is used worldwide, so the PLMN is important to the app for other reasons. You talk to the guy in charge.. he's rumored to have two research papers due tomorrow, but spending a lot of time procrastinating! (I hear there aren't any beta crew spots open at the moment but he appreciates your interest.) -Mike
  22. mikejeep
    Bite your tongue! Nah, I broke something silly, already fixed it for the next version. The app recognizes B41, but I forgot to have the display show that on the main screen.. clearly not very helpful. Thanks for the PM too. Band 26 should display correctly in both the pulldown and the main screen. I must have been more awake when I finished that section. -Mike
  23. mikejeep
    It's a known issue.. I broke it in 4.24. You'll see B41 in the notification pulldown if it's active, but not on the main app screen. It's one of numerous fixes I have been working on over the past couple of days. Keep an eye on the changelog on the website for updates; I've gotten most of the bugs fixed and in testing already, but there are still a couple more things I need to resolve. -Mike
  24. mikejeep
    Ditto, and I had refreshed it a few times just in case. Must have multiple servers and it took awhile. It's still a typo anyway, the current version is KOT49H, not KRT49H. -Mike
  25. mikejeep
    KTU84F still shows up that page for me.. and Sprint can post anything they want, it's up to Google to push out the update. The important page is here: https://developers.google.com/android/nexus/images#hammerhead -Mike
×
×
  • Create New...