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
    There is a difference between "its here" and "its gonna be deployed soon". We don't need "top of the top" management to tell us that 800 MHz service is coming.. we already knew that -Mike
  2. mikejeep
    No, I don't think I can do much with that.. the app is pulling the ID the only way I know how to, but for some reason it doesn't always match what is displayed on the engineering screen. They are usually identical, but not always. Based on what I've seen, I would estimate that they match about 80% of the time. There is a delay in updating it sometimes, and I have no idea why. I don't have any way to know which one is correct; I assume the engineering screen is more accurate, but that is just my own guess. -Mike
  3. mikejeep
    Does GPS work for you on deck's build? If so, that and the patch above should get you the best of everything. -Mike
  4. mikejeep
    Hmm.. I didn't touch any of the code that pulls the GCI from the new LTE functions in Android 4.2+, so perhaps it's something in the CM nightly you're running. I have been trying to take the leap from Sense to CM 10.2 on my EVO this week, but something I'm restoring from my TB backup is causing a bootloop, so I can't tell you if it works for me or not. I do recall seeing something about the 10.2 releases having a lot of issues, and the consensus seemed to be that deck's 8/24 release was the most stable. Is that what you are running? -Mike
  5. mikejeep
    I was referring to the same thing.. granted, my area was a First Round market, but still, progress has been steady and roughly in line with what I expected. A majority of sites have been 3G accepted for quite some time around here, and as that work winded down, the LTE acceptances started to come in. I did expect a little more progress this summer, but the sites that have been accepted are providing a decent LTE coverage area from what I've experienced. The pace does not seem to be noticeably behind any other areas of the country (besides those lucky folks who have Shentel). -Mike
  6. mikejeep
    Peabody!!! Gee that is impressive.. that 620-mile shot just might beat digiblur's record for furthest distance from an 800 site..... -Mike
  7. mikejeep
    Really? I've been pretty impressed with the speed and quality of the ALU rollout around Boston.. I take it you're less-than-satisfied with their work in the Southwest? -Mike
  8. mikejeep
    I wouldn't be surprised if things have improved since then. I've been to about 10 games at Fenway this year, and the game I was posting about last week was the first time I have had such great service at the ballpark. The NV progress is definitely noticeable. -Mike
  9. mikejeep
    I believe Sensorly data is uploaded based on the network information the device is reporting, such as the MCC/MNC.. Sprint devices are on 310120 while connected to standard 1900MHz LTE, so if your Boost phone shows something else, it's probably not going to show up on the Sprint maps. I don't see any Boost-specific maps on Sensorly's website. -Mike
  10. mikejeep
    I am willing to bet that all 3 instances of 800 that you saw were legitimate. A usable 800 SMR signal has shown to work over much greater distances than most of us are used to seeing with PCS. A lot of 800 upgrades are in progress, even though the S4GRU maps might not seem to show too much activity right now. You are probably only catching quick glimpses of the signal because you have a stronger PCS signal from closer sites that your device is selecting. Around the Boston market, I am on 800 often and all of the site information is identical to what shows for each site on the 1900 MHz side, except for the SID. Glad to hear the app is giving you some good news! It will only get better... -Mike
  11. mikejeep
    Will do.. congrats! I'm getting married later this month myself, but I'm not going to let a minor detail like being completely broke keep me away from the Garden! -Mike
  12. mikejeep
    Hmm.. I thought I had a workaround for that bug, but I guess it's not working. Samsung likes to be difficult! I will check into it some more. -Mike
  13. mikejeep
    Yep, several people did.. not trying to be rude, but if you just look a few posts ahead of yours, it's all there. There is an update to the update. Check Google Play, you should see a newer version that fixes it, 4.14. -Mike
  14. mikejeep
    Phew! That should solve your problem. It is off by default.. -Mike
  15. mikejeep
    Ugh here we go again with the stale LTE signals! Boooo.. I think your EVO LTE will be fine, that's my primary testing device and I have never seen that bug on it. Do you have "Show hidden data" disabled on the Preferences screen? -Mike
  16. mikejeep
    Yeah, that would be the cause.. I will see if there is anything I can change on my end to prevent this from happening to you (and anyone else). The issue is my app says, "Hey, we want to open up this link, where's your web browser?", and on your device, it looks for the HTC Linkify stuff to get the answer to that question. No Linkify, no answer, force close. Thank Apple. -Mike
  17. mikejeep
    Hmm.. not on any of the devices I tested with, including an EVO...? Didn't touch anything on the About screen recently, so if it's a bug, it's not new. I did some research, and may have figured out what is going on.. did you by any chance tinker with the HTC Linkify stuff that was implemented to satisfy Apple's patent complaint? The app tries to fire off your default browser, but on HTC devices, it appears to need to go through that Linkify app first.. -Mike
  18. mikejeep
    None at all? Or it is stuck on "Click for map..."? If it's stuck, reboot your phone. That's a well-documented Android bug that drives me crazy. Something happens with the geocoding routine and only a restart will resolve it. One of the goals of implementing the BSL address cache was to make this bug become a non-issue most of the time. If you have an address cached, it doesn't matter if the geocoding routine has shut down, you'll still see it. -Mike
  19. mikejeep
    SignalCheck Pro 4.14 has been pushed to Google Play. The issue with invalid or missing EV-DO and LTE information introduced in the last version has been fixed.. shout out to lilotimz for his troubleshooting help in The Lounge tonight to get this working! Also, I put 'x' in front of the hex BID for now. We can continue to discuss it, I'm good with whatever style you guys prefer, including switching it back to nothing at all. My initial concern was that it was the only unlabeled item on the screen; not specifically concerned that it's hex, just that it's a piece of information without a label. But the more I think of it, I don't necessarily think it needs to be explained. You guys tell me what you want. I don't think it needs to be a preference setting though, so don't go there -Mike
  20. mikejeep
    Wait.. it was from 4.09? I've been flooded with reports of similar issues with 4.13, but nothing about the version before it. Now that my trip to the Cheesecake Factory is over and I'm full, I'll be working on a fix. kckid or any other Pro users who are having issues, I'll be lurking in the lounge if you want to help me out. All 3 of my devices are working properly so it's tough to troubleshoot. -Mike
  21. mikejeep
    Uh oh, I think I broke something related to EV-DO/LTE signals in the latest update. kckid is not the only one having issues. It is a bug in the app, but it only affects some users. I am not home, but I think I know what the problem is. I will get on it when I get home in a few hours. -Mike
  22. mikejeep
    I try to look at it from a "lowest common denominator" point of view: those of us who follow this thread know it's the hex value, but just about everyone else probably doesn't. Throwing the 0x in there provides a hint to the confused user. It doesn't have to be "0x" if someone can think of a better alternative. I thought of putting "h" on the end too.. trying to find the cleanest accurate look. When the cache is created on a device for the first time, the app's version number at the time is captured. If it's not 4.13 or newer, it deletes it: -Mike
  23. mikejeep
    Funny, I spent quite a bit of time trying to figure out a simple way to indicate the hex value without cluttering up the screen, and couldn't come up with anything.. duh. Anyone have a good reason why I shouldn't do this? -Mike
  24. mikejeep
    I was too slow in checking the trivia post to give an answer that didn't look like cheating, but I did notice it too! Relieved to see that it's just a testing thing, I was going to get mad if Sprint was going to start using PCS SIDs for SMR.. -Mike
  25. mikejeep
    SignalCheck Pro has been updated to version 4.13 on Google Play.. it should be available within the hour. The changes are below; big thanks to 4ginnc for his help in troubleshooting the cache bug! Resolved issue with incorrect BSL address cache entries. (Pro) This is the most significant reason for this release. Those of you who follow this thread are aware that a bug was discovered in the BSL address cache introduced in the last version of the app. If a BSL address response came after your device had switched 1X sites, the wrong coordinates were being attached to the address in the cache. This has been fixed; upon installing this version for the first time, your cache will be wiped clean to eliminate any possible entries that were saved incorrectly. Added hex value of BID on main display. Users asked for it, so here it is! Corrected LTE sector ID fields to display as “GCI” (Global Cell Identity) instead of “Serving Cell” or “CID”. The technologically correct term is GCI, so that's what it's labeled as in the app now. Resolved crashes on GSM devices when the MCC/MNC was invalid. Some crashes were reported by GSM users starting with the last version; these should now be fixed. Updated numerous entries in the CDMA and EV-DO carrier databases. Revol Wireless should now display properly; there were a few other minor updates as well. Thanks for all of your support! SignalCheck Lite will be updated to 4.13 sometime next week. -Mike
×
×
  • Create New...