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
    Whenever I can finally figure out how to get the data (so frustrating ), I should be able to add those to the status bar. It gets a bit cumbersome because each number is its own separate graphic (if there are 500 possible PN's, that's 500 graphic files), but as long as it doesn't bog down the app, I would do it. With more Android 4.2 devices coming out, I'm hopeful that manufacturers will start using the built-in functionality to display the Serving Cell instead of relying on manufacturer-specific reflection hacks to do it. I haven't given up on Samsung yet though.. -Mike
  2. mikejeep
    Hey, you should have seen my eyes pop out when I read your post.. I don't like feeling responsible for almost bricking someone's phone! I'm glad you were able to get it back online.. and whatever four-letter words were directed towards me in the meantime were well deserved. I don't normally use the 1X notification icon, so I forgot to test it. Funny how two letters buried in thousands of lines of code can wreak so much havoc.. Seriously, to all of you, I'm humbled by your kind words and support.. the S4GRU crowd has been awesome from the beginning. I never thought this app would get so popular, but I'm so glad that others find it useful. The free version now has over 6,000 total installs, and is growing at 100+ per day and climbing, which I think is amazing. Good stuff! -Mike
  3. mikejeep
    Just saw this.. sorry to hear you got hurt, get well soon! The Golden Rule is to go home at the end of your shift -- you are a wise man. I destroyed my knee at work last weekend.. going in for ACL surgery at the end of next week.. out of work until at least New Years. I try to put a positive spin on it.. decided to start working on my master's degree, and have more time to waste on S4GRU! Hang in there! -Mike
  4. mikejeep
    You got the special "Chicago" version of my app. Don't update to 3.15, yours is supposed to blow up your phone Heck of a game the other night, but don't get too excited. We were down 0-2 to Vancouver in the 2011 Finals and it was no big deal.. and down by 3 goals with 10:00 left in Game 7 against Toronto this year and it was no big deal.. and unlike the Hawks, we can win playoff games on the road! -Mike
  5. mikejeep
    It was a two-letter typo in the 1X notification code that caused all the problems! Version 3.15 has been uploaded to Google Play already, it usually takes 10-60 minutes to become available. For the next couple of hours, do not update unless you know you are getting 3.15. If you have already updated to 3.14, keep 1X notifications disabled and you should be ok. Sorry for the trouble, especially for those of you who had serious issues this morning! -Mike
  6. mikejeep
    Uh oh! I didn't have any issues like this on my devices, and I've been running this new version for awhile. Taking down the update right now and I will see what is going on. Sorry! -Mike
  7. mikejeep
    SignalCheck Pro version 3.14 has been released on Google Play! It should be available within the hour here. This version is mostly just bugfixes and minor tweaks, and will likely be the last version to support Android 2.1. The new ringtone selector will require some features from Android 2.2+, and is not ready for the public yet. It's almost done, but still in beta testing for now. Here is a summary of the changes in this version: Resolved issue with Sprint 800MHz SMR alerts not working. (Pro) I broke this in a recent release when trying to fix simultaneous LTE and 800 alerts. It should be fixed, but this is one area that I would appreciate feedback on, since 800 service is still relatively rare. Resolved issue with Reset Data Connection button displaying at the top of the screen on GSM devices. (Pro) Us Sprint users wouldn't have noticed this, but AT&T, T-Mobile, and European folks did. Resolved issue with upgrade banner display blocking info on small screens. (Lite) This only affects people with small screens running the free version; the upgrade banner blocked the bottom of the screen. It now fits at the bottom of the window, and will scroll down if necessary. Resolved issue with SID/NID/BID/BSL fields not updating while on a telephone call; these fields are not updated by the system during an active call. Fields will now be hidden during calls to prevent display of invalid data. This bug was discovered by WiWavelength (thanks AJ!). Apparently most (if not all?) Android devices do not update this information during an active telephone call, so if you are on the phone and still feel the need to stare at your signal information, you will see these fields are gone. As soon as the call is disconnected, they will update and magically reappear. Adjusted alerts to reduce occurrences of sounds "stuttering" or quickly playing several times in a row. (Pro) Due to the way devices connect to the network, there were times when you might have heard a few alerts at once, overlapping or stuttering, especially when reacquiring a lost signal or coming out of airplane mode. The code has been improved to prevent most of these occurrences. Adjusted layout to prevent scrollbar on 4" screens in most circumstances. Not a big deal, but the little things bother me. It only required shifting things by a few pixels, and I guarantee that none of you would have noticed if I didn't point it out here. Added error display and help screen to notify user when BSL geocoding is failing. (Pro) A documented Android bug causes problem with the geocoding functions; for no apparent reason at all, it will suddenly stop working, and only a full restart of the device resolves the problem. If you have seen the "Locating..." message stay on your screen for awhile, you might have experienced this. A clickable error message will now appear if there is no response from the server after several tries. Clicking on the error will explain the possible causes for the problem. No matter what, the app will continue trying to reach the server, in case it is a network problem. SignalCheck Lite (the free version) has not been updated yet, but will be available by the end of the weekend. Comments/bugs/suggestions/etc are welcomed as always, and feel free to post a review on Google Play if you are inclined to do that sort of thing! Many of you have already done so, and I sincerely appreciate it. -Mike
  8. mikejeep
    Areas very close to you received LTE before 95% of the country did, and it's a nationwide project that was scheduled to take two years. Relax. They are working on it. Urban areas are typically more complicated, which could be why the suburbs were built out quicker early on, and you have seen "zero progress" since. You have made a total of 11 posts here, 9 of which are just complaining about how badly you think Sprint is handling their network in your specific corner of the world. Feel free to switch to one of the other providers that you like better whenever you like, but in the meantime, please do your whining elsewhere. This is not the forum for that. -Mike
  9. mikejeep
    Something tells me that the LTE network will be significantly complete before Sprint gets anywhere near pulling the plug on Wimax.. the pace of the NV rollout is steadily cruising along, and I don't see Sprint making a PR blunder like wiping out existing 4G customers these days. -Mike
  10. mikejeep
    Hmm. I tested numerous times tonight, and could not get it to launch at startup unless it was checked off, even with a fresh install. Try going into Settings -> Apps -> SignalCheck Pro, and click "Clear data", then go back into the app and uncheck it from the Preferences screen. If anyone else is having the app start up at boot, but you have the setting disabled, please holler! -Mike
  11. mikejeep
    Something similar was suggested previously and is already on the list. I love the idea, especially right now while we are in the midst of the LTE rollout. FYI, I haven't been too good at advertising this, but I do keep an updated "wishlist" and changelog at http://www.bluelinepc.com/signalcheck/. The wishlist is roughly prioritized, with things I consider most important at the top. Between releases, I keep the changelog current to show what will be coming in the next version. -Mike
  12. mikejeep
    I can never have too many suggestions! More is better, like the AT&T guy says.. that way, when someone suggests something easy, I feel productive! Some form of logging is in the early stages of development.. I'm in still working out the details, but I will make note of your suggestions. Don't tell anyone I said that, or everyone will start asking for it! -Mike
  13. mikejeep
    Certainly! Sorry, didn't know that was happening.. has it been like that all along? Are you running 3.09 now? -Mike
  14. mikejeep
    Nice pictures, kind of cool to get an up-close look at the nerdy nitty gritty. Sure, RF amplifiers isn't correct, but at least it was an overall positive-spinning Sprint article instead of the usual. Kudos to Sprint if they actually did reach out and invite her up to that roof to see progress. Oh, and whoever gave SignalCheck the shout-out in the comments section there is my hero! -Mike
  15. mikejeep
    I'm jealous of you guys. Update coming soon, just stuck on fine-tuning this annoying new feature I finally got working, you know, the one that lets you choose any notification tones you want... -Mike
  16. mikejeep
    I figured out a way to do some realistic testing tonight and figured out what was going on with the 800 SMR alerts... they are, in fact, broken! They worked in an earlier version, but I broke it when trying to resolve an issue when more than one alert arrives simultaneously. I'm working on a fix.. -Mike
  17. mikejeep
    I have noticed that the site briefly goes down shortly after 1:00am Eastern Time quite often. Initially, s4gru.com is completely unreachable, then it comes back online with the Internal Server Error message you posted, then it goes back live. Usually only happens for a few minutes, and I can't say that I've seen it consistently every night. Definitely saw it tonight. Go pour another beverage of your choice, come back, and by then it's back again. -Mike
  18. mikejeep
    Suddenly several sites in the Andover/Tewksbury/Wilmington/Woburn area that were LTE or eHRPD are back to EV-DO or 1X.. I'm thinking its a good sign! -Mike
  19. mikejeep
    Hmm.. the correct answer was no, you are not a Blackhawks fan (the hockey team.. most likely about to play my hockey team for the Stanley Cup. It's a big deal if you waste as much time watching sports as I do). I'll allow it this one time! Did you change anything on your phone around the same time the SID/NID/BID and BSL stopped showing properly? Updated phone software.. updated SignalCheck.. or anything else you can think of? Something must have triggered it to stop working. I just hopped in "The Lounge" chat room if you want to discuss with me live, I'll be online for a few more minutes. You can access it from the bar near the top of the screen, you might have to click "More". -Mike
  20. mikejeep
    Of course you're doing something wrong.. my app is perfect!! Hmm.. no something is definitely wrong. Your device seems to know it's on SID/NID/BID 22439/221/28881, however SignalCheck is seeing all zeros for those values. That has a domino effect on other aspects of the app, so we need to figure out why that is broken before trying to fix anything else. A few questions for ya... Do you have 1X geocoding turned on in the preferences? Have you tried rebooting your device? Do the SID/NID/BID fields ever show anything besides zeroes? What ROM are you running? Are you a Blackhawks fan? We'll get it sorted out! -Mike
  21. mikejeep
    Hmm.. post a screen shot when you get a chance. Is it a nightly or something similar that is still in the early stages of testing? I've been working on nothing but hammering away at the Samsung-specific stuff for the past few weeks, but I might have to set that aside temporarily to let my frustration with it settle down. Not much progress and zero cooperation from Samsung. -Mike
  22. mikejeep
    Jeff, the app was showing "1X 800" on the top left, correct? If you are near an 800 site again, try disabling all LTE alerts but keep the 800 alert on.. see if you get it then. When I was trying to test it out, the LTE alert was overriding the 800 alert, but I thought I fixed that. I don't have any live 800 in my area, so its tricky for me to test. -Mike
  23. mikejeep
    Aha, thank you AJ -- so in plain English, this is when a telephone call is active? I just did some similar testing with my EVO LTE; it definitely does not update the BID or associated site coordinates while on a call. As soon as I hung up, it immediately showed the correct information. The signal strengths do appear to properly update. I watched the "Radio info" screen as well, and that did not update the BID until ending the call either (after some confusion, I realized the ID is in hex on that screen!) Yes, the BSL is tied to the BID -- when the BID changes, it refreshes the BSL address. However, since it appears that the coordinates do not change either, forcing the BSL to update more frequently will not do anything. Do you care to guess if this issue is device-specific, ROM-specific, carrier-specific, or Android-wide? Or is it the way the CDMA protocol behaves by design? If it's a bug in Android, I wasn't able to find any evidence that it has been pointed out by anyone else. Not sure of the best approach to compensate for this in my app, since I'm relying on the fact that the information the device is providing is accurate. It continues to update the screen while on a call, but some of the data itself is stale. I will start looking into a method to determine if a call is active and tweak the display accordingly for now.. Thanks for finding the bug! -Mike
  24. mikejeep
    Interesting thought! I think that might be do-able.. I will put it on the list. Hmm.. I've never looked into any of the headset/Bluetooth features, so right now I can't say how feasible that is. I can certainly look into it.. worst case scenario, its something to work on after I tackle some of the higher priority items. This has been at the very top of my priority list all along; it has been discussed here several times. There is some sort of Android bug preventing the standard method of implementing this from working correctly in my app.. I am constantly researching this and trying to get it working. Thanks for the compliments and suggestions.. much appreciated!! -Mike
  25. mikejeep
    Thanks Eric! I initially considered adding some Wimax features, but it appeared to require proprietary manufacturer-dependent code that would be complicated. Plus, LTE is obviously replacing Wimax and I wanted to spend more time in that stuff. To be honest you are the first person to ask for it too -Mike
×
×
  • Create New...