Jump to content

mikejeep

Honored Premier Sponsor
 View Profile  See their activity

  • Posts

    3,264

  • Joined

  • Last visited

  • Days Won

    186

 Content Type 

Everything posted by mikejeep

  1. mikejeep
    Not unless its running a flavor of Android 4.2 that has that functionality. Google put the framework for LTE Cell ID in 4.2, and SignalCheck includes the code to display it. Unfortunately, I haven't found any devices (yet) that use those functions. The app will hide the data if it is invalid. The free version will show whatever LTE cell information the app is capable of extracting from your device. That code is exactly the same in both versions. Most (if not all) HTC devices will show you the hex LTE ID thanks to the efforts of lordsutch, a user on here. I'm currently working on getting similar functionality for Samsung devices, but its not fully working yet. It basically involves going in the "back door" so its a lot of trial and error. Once I make useful progress, I will mention it here first! -Mike
  2. mikejeep
    Thanks! I have not noticed any extra battery drain myself, and nobody has seemed to mention it. The app doesn't do any heavy lifting behind the scenes. Leaving the screen on (as with any app) would be the only cause for more battery drain usage. -Mike
  3. mikejeep
    LOL trying to force my hand, are you? They just activated that feature for me yesterday; this morning I started setting it up for my small group of beta testers, but until I start playing with it some more, I'm not sure how it works. It looks like access control will be through Google Groups; this means I either have to invite each person individually by e-mail address, or keep it open it to the public. I'd prefer to spend what little free time I have to devote to SignalCheck spent adding more features instead of tackling administrative overhead. That being said, I have already given some thought as to how to use this to hook up S4GRU Premier Sponsors. S4GRU is probably my biggest userbase, and I'd love to try and 'throw a bone' to those who have helped out this site the most. I'd be most willing to go this route, but I need to figure out the logistics first. I announce new versions here on S4GRU first, usually immediately after I finish uploading it to Google Play. Also, Pro users get updates a few days in advance of Lite users. I don't want to release updates too often and annoy people, but at the same time, when I have a few useful things ready to go, I update the app. I wish I could say that I have a whole pile of awesome features that I'm holding back from you guys, but I promise, whatever I have working is in the latest release of the app! -Mike
  4. mikejeep
    Update time!! SignalCheck Pro 3.09 is ready for the masses, and should be available on Google Play shortly. I was hoping to include more new features, but I haven't had much free time lately and I wanted to release the few things that were finished. Here are the changes: Resolved issue with “null” appearing after the LTE SNR reading on some devices. Resolved issue with SignalCheck not launching automatically at boot in certain situations. (Pro) Resolved issue with widget appearing as 2×2 instead of 1×1 on some devices. (Pro) Added support for Samsung’s Multi Window (aka multi-view) feature. Added option to allow SignalCheck to display in portrait or landscape mode according to how the user rotates the device. (Pro) Added address text to BSL marker in Google Maps. (Pro) The Multi Window feature is pretty neat, and I'm glad some of you brought it to my attention. I will work on getting the free (Lite) version updated and published soon. On another note, I know many of you have Samsung devices, and getting extra features to work in the app for those devices has been challenging because I was essentially working blind, since I have an HTC. Well, I want to take a moment to give a huge shout-out to Robert for going the extra mile (which he seems to do for all of us a lot) and helping solve that problem. Last week, he shipped me his spare Samsung Galaxy Victory so I could borrow it for development purposes. Considering how much he already does for everyone, it was quite a gesture.. digiblur deserves credit for making it happen too. Having a Samsung device in my hand should help me figure out how to pull more information out of those devices, and make this app even more useful. Thanks Robert!! I'll be focusing my efforts on tackling Samsung-specific stuff for the next release. -Mike
  5. mikejeep
    SignalCheck shows you whatever the device is considering to be the currently active CDMA cell. It doesn't do anything fancy with the information.. just displays what Android thinks it is connected to. It's funny, I had never watched the app while I was on a call either.. so I just tried it. The 1X cell never changed, which is a little odd considering that when I am at home, I usually see it fluctuating fairly often when I am watching the app. I am on top of a large hill with a big window facing a tower that is not usually the one I am connected to; however, walking over to the window almost always forces it to switch to that site. Very handy for testing my app! While on a call, it didn't do that, it stayed with the site it was on when I made the call. Shortly after I hung up, it casually flipped between a few different sites. It certainly could just be a coincidence though. -Mike
  6. mikejeep
    You nailed it. Once SignalCheck gets valid coordinates from a site, it queries a Google reverse geocoding server that translates the latitude/longitude into a street address. If you are switching sectors very quickly, you could be switching before the query results are returned. SignalCheck only sends the query if the BID has changed. There is an Android bug that effects all apps on all devices which will randomly cause this to stop working and display "Locating.." forever (see my post from a few minutes ago). If you are experiencing this, the only fix is a reboot. -Mike
  7. mikejeep
    There is a well-documented (and very annoying) Android bug that essentially causes the location service to fizzle out sometimes, and the only fix is to reboot your device. Many developers have tried workarounds, but nothing has worked. Google is aware of the issue, but nobody knows why it hasn't been fixed. I should probably document this somewhere so users are aware of the issue. Another theoretical possibility is that it was unable to connect to the Google geocoding server, which could either be a problem on your end or Google's. It attempts to query that server whenever the SID changes or SignalCheck is brought to the foreground. Unless you are unable to access the Internet on your device, I would say this is not the problem. Try a reboot.. -Mike
  8. mikejeep
    Do you have something that would play a sound effect when you roam? Unless your phone reported a quick glimpse of 800 right before it went into roaming, I don't think the sound came from SignalCheck.. -Mike
  9. mikejeep
    Understood. I've been pleasantly surprised by the 3G speeds lately.. there have obviously been a lot more 3G sites accepted around here at this point, but I agree, if you are stuck in pre-NV 3G areas, you should have held on to Verizon for a bit longer. I hear what you are saying about Sprint; I have been a customer for over 10 years, and have been very happy with their customer service, devices, and pricing the entire time. The actual cellular service has been acceptable for a majority of my needs, but its certainly not perfect and I benefited from always having good service near my home and work, including LTE very early in its deployment. I understand that I am one of the luckier ones.. its easier for me to be patient as NV rolls out because of that. I think Sprint still has their 30-day bailout policy, so you should be able to switch back without penalty if you want to. Not sure how that might affect your eligibility for new customer promos in the future though. -Mike
  10. mikejeep
    Tapatalk ate my post. Will edit from a computer in a minute.. EDIT: What I was trying to say (for future readers of this thread) was that I have had some success setting my EVO LTE to "CDMA, LTE" mode on the radio info screen. This forces your phone to ignore EV-DO signals, resulting in more frequent LTE connections, even if the signal is poor. Of course that depends on the coverage in your area.. if the 4G just isn't there, you will be on 1X the entire time. -Mike
  11. mikejeep
    It's getting there.. every tower along Route 3 has 4G accepted; I haven't paid close attention, but it seems like around here, once 4G is accepted, it is accessible. Most of Lowell is covered, Tewksbury has 2 towers live, and 4G started broadcasting from the tower at the Dascomb Rd exit off 93 last week. I'm happy with the progress, but don't know if its worth jumping carriers right this second, unless you have other reasons. LTE coverage is still filling in. Check Sensorly, its the best source for true signal strengths out there. -Mike
  12. mikejeep
    I haven't had much LTE progress around here lately, so not much has changed. I spend 90% of my time in areas where LTE is available though, and I found that switching the radio mode to "LTE, CDMA" was surprisingly not a bad idea. It basically forces your phone to either 1X or 4G, never connecting to 3G. As a result, it always holds onto an LTE signal, no matter how faint. It works well for me, but only because of the way the coverage is in my area. If I was stuck on 1X more often, I certainly wouldn't do it.. 3G is much faster than that. As far as your bookmarks question, I'm not sure what you are asking...? -Mike
  13. mikejeep
    I upgraded to Jelly Bean last week, and the contacts delay problem is completely fixed.. everything else works well too. No complaints. -Mike
  14. mikejeep
    I'm starting to notice something similar; some of my BSL's have changed slightly, which I'm guessing is the result of different latitude/longitude values being broadcast, hopefully due to new equipment. Unfortunately, these new addresses are still offset in my area. Rats. Thanks for your support -- I promise I will spend wisely.. LOL Yes, each sector has its own BSL.. so your theory is correct. In my area, all the tower locations are offset; therefore, it looks like there are lots of towers scattered everywhere, when in reality, the towers are not at any of those addresses. Some folks (like Jeff above) get the actual tower address.. lucky them. Each sector should be broadcasting a different BID.. if you are seeing multiple addresses for the same BID, that is most likely an issue with Google's server that converts latitude/longitude into street addresses. It seems to get less-specific with the address occasionally, perhaps when it is overloaded. Nothing any of us can do about that. -Mike
  15. mikejeep
    Woohoo! I had downloaded the MD4 source code and was going to start picking it apart tonight.. thanks for the update, you just saved me a lot of time. -Mike
  16. mikejeep
    Not sure what you were originally posting, but weren't you seeing -1 for NID/SID/BID before? Did it fix itself? Fingers crossed... -Mike
  17. mikejeep
    Not sure where you are getting that feeling from, but hey maybe you know something the rest of us don't.. otherwise, I suggest that you take some time and read some of the other threads on this forum before jumping to conclusions like that. This isn't something that will happen overnight. Nothing has been left half completed.. its either in progress or hasn't started yet. I don't consider the current rate of 1000+ upgrades completed per week as anything but positive. -Mike
  18. mikejeep
    Relax. This is a multi-million, multi-year, nationwide project to upgrade tens of thousands of cellular sites. Many areas of the country haven't seen any upgrades at all yet. MA is one of the lucky areas that started early on in the project. There is a TON of work involved. State and local permits, angry neighbors, cooperation and coordination between many different vendors, different contractors, birds, weather.. lots of things. Be patient. Its coming. Search anywhere on this forum and you will see the same message being relayed to everyone across the country. -Mike
  19. mikejeep
    Someone else had recently asked for "multiview" support and I hadn't had a chance to figure out what it was yet.. that link was very helpful. I only glanced at it briefly, but from what I saw it shouldn't be too tricky to add support. I'll need someone with a compatible device to test it out, so if you are willing I will send you a message when I have something usable. -Mike
  20. mikejeep
    Oh no! I don't have a Samsung so I'm not totally familiar with their updates; is that a stock update of some sort? If you could describe what it is (firmware, radio, etc) I will look into it. -Mike
  21. mikejeep
    Far more often than I should.. many "quick" errands have turned into lengthy tower hunts, haha! -Mike
  22. mikejeep
    Try disabling the LTE alerts and see what happens... -Mike
  23. mikejeep
    Did you get it yet? Let me know how it works.. interested to see if any of the "extra" features working on other HTC devices will work on the One, specifically the LTE Serving Cell... -Mike
  24. mikejeep
    Thank you for the screenshot!! Hugely helpful. Are you sure you had audio and/or vibrate alerts enabled for 800? It's separate from the LTE alerts. Also try disabling LTE alerts in case both signals are being discovered at the same time and perhaps overlapping.. if you're seeing that "1X 800" label, the alert should be triggering. -Mike
  25. mikejeep
    Cool, I was wondering how it would behave on a disconnected device! Was there a 1X SID showing up when you were on 1X 800? Were you definitely on an 800 connection at the time?
×
×
  • Create New...