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
    I had explicitly disabled Landscape mode (I knew what you meant!), because, Android essentially re-launches the activity if the screen orientation changes, which causes the "Please wait" screen to appear (however briefly) until the phone receives the next signal update. There is no benefit to forcing an update, because SignalCheck automatically updates the data the instant the phone makes it available; if your signals go 30 seconds wihout updating, it will take 30 seconds for the app to show any data. I may be able to add it as an option that users could choose to enable though; I will see what I can do. Not sure what the dual view mode is but I'll look into that as well. I could consider doing an overlay if some would find it useful as well, but I feel like the notification icon can serve that purpose as well. Hmm. What ROM are you running? What version of Android is it? Does it freeze up if only 1 or 2 of those apps are running? SignalCheck doesn't really 'check' anything; it sits back and listens for the phone to push out data updates. In all of my testing, it has a minimal impact on CPU and memory. I have no idea what waze and Sensorly do behind the scenes. -Mike
  2. mikejeep
    I was in Downtown Boston at mile 25 when it happened (Kenmore Square for you locals). Was with family waiting to see my sister running. Thankfully she tweaked her knee around mile 15, and slowed her pace... otherwise she would have been at the finish line at the exact wrong time. They shut down the race as she passed mile 24. Anyways, My phone performed better than I expected.. I had trouble making one call, but other than that, my phone was texting/ringing/dialing non-stop for a solid 2 hours before the battery had enough. Facebook and Google Maps were a little slow but not unusable. Others I was with seemed to have more problems than me, but I don't know who had what carrier. Text messages seemed to be flowing without any issues for everyone. Just want to say all of the police/fire/EMS/race volunteers did an unreal job. Except for the first few minutes at the immediate scene (completely understandable), there was virtually no panic; some people were crying, but for the most part it was just an eerie quiet as everyone followed the directions of the public safety folks trying to clear the area. They messed with the wrong city... -Mike
  3. mikejeep
    Thanks for the kudos! I'm not familiar with Tasker, but I will check it out and see what I can do.. sounds like you have created a pretty efficient way to map LTE. Not sure if it helps, but if you enable either LTE alert, a separate notification is created. -Mike
  4. mikejeep
    SignalCheck Pro 3.06 has been released and should be available through Google Play shortly. Some shiny new features are in this release, including the following: Resolved some issues with false LTE readings on CM10.1 ROMs. The root cause of CM10.1 folks seeing strange LTE values is beyond my control. SignalCheck displays the signal information the phone is reporting. This "band-aid" fix will hopefully resolve a majority of these issues. Feedback from CM10.1 users would be appreciated! Resolved issues with crashes caused by invalid latitude/longitude values. Some carriers are apparently broadcastin invalid location values, which was causing the app to crash. This has been fixed. Added a configurable SignalCheck widget. Well here's something new! A 1x1 widget, displaying realtime information, updated as quickly as the main app. Connection type is displayed, along with up to 3 signal strength readings. Connection types are colorized to match Sensorly maps.. so 1X = cyan, 3G = green, 4G = purple. Signal strength readings are colorized based on good/fair/poor signals; good = green, fair = yellow, poor = red. Clicking on the widget will either bring SignalCheck to the foreground (default), or reset your data connection. This can be configured through the "Preferences" menu. SignalCheck must be running in the background in order for the widget to update. If you shut down SignalCheck, the widget display will automatically change to a message indicating that the app is not running. Added options for Sprint 800MHz 1xRTT connection alerts. Hey look, something else new! Anywhere 1X information is displayed (including on the new widget) will indicate "800" if connected to a new Sprint 800MHz 1X site. Users can also configure audio and/or vibrating alerts to notify them when an 800 connection is made. Please note that this feature has not been tested out on the street yet due to the limited areas 800 service is active right now, so please provide any feedback you can. Added option to display EV-DO sector ID (only for HTC devices at this time). Not sure how useful it is, but it's there if you want it. I find it useful just to see when the EV-DO site changes. Clicking on 1X BSL address now launches Google Maps (or other mapping app) with base station marked. It will launch whatever mapping app you have set as the default for your device. The address is underlined to hint that its clickable, in case you forget. Alerts no longer require any status bar icons to be active. Alerts and status bar icons are now separate and do not rely on each other. Users could disable all status bar icons and the app would continue running in the background until 'Exit' was selected. This would keep alerts available and the widget updated, but not take up any room in the status bar. 1X icon no longer requires the main status bar icon to be active. Each status bar icon is now separate and do not rely on each other. As always, please post your comments and bug reports here. I could not test the CM10 and 800MHz updates myself, so I would especially like to hear about those features. The update for SignalCheck Lite is in progress and should be up this weekend. The S4GRU crowd is my best (and probably biggest) user base -- I appreciate you all! Thanks, -Mike
  5. mikejeep
    I have been working on this, among other mapping-related ideas.. glad to see someone would find it useful! The hard part is that each "thing" you see in the notification bar is actually a graphic, not text. Every signal reading (-99, -100, 101...) and network type is a separate image. I'm trying to learn how to dynamically manipulate images, with the goal of eventually allowing users to choose their own color. For the record, the official Android UI Guidelines specify that status bar icons are to be white/gray.. but I know many custom ROMs use other colors. Oooh now you're thinking! I know what you are looking for here. Been experimenting with logging various pieces of data, this could work nicely. Added to the list. You might have just scored a big win for the Samsung folks.. some of that info on your XDA thread looks like it might point me in the right direction to get some functionality similar to what HTC users have. I will start playing around with it; if I come up with something to test, I will shoot you a PM. Certainly let me know if you come up with anything on your own and you want to share it. Thanks for the suggestions! -Mike
  6. mikejeep
    I wonder if there is a way to "set" the RSRQ or SNR values through code.. essentially fool the EVO by feeding it "good" signal strengths, therefore having it choose/hold LTE more frequently. My EVO seems to pick up and hold onto LTE fairly quickly once I enter an LTE area.. my issue has always been that sometimes data transfers stop after being connected to LTE for awhile. The phone appears connected, but data won't flow in either direction until I toggle airplane mode. Not sure if that's the exact issue others have or not.. I just keep LTE off or deal with it. Until recently, it wasn't a big deal to me because there wasn't much LTE in my area. Now its getting annoying! -Mike
  7. mikejeep
    Sorry to hear that, but at least its not a bug I have to figure out how to fix Are they giving you the replacement under warranty I hope? -Mike
  8. mikejeep
    It could be that, but which device do you have... looks like an EVO LTE on a stock ROM? If it's something else, let me know which ROM and what version of Android it is running. There have been wacky LTE readings on devices running CM10.1. You say the strength varies each time, but once it connects, does the strength ever fluctuate before disappearing? I'm intrigued by the fact that you're getting a Serving Cell; that leads me to believe that you're hitting an actual tower.. Your device wouldn't just make that up; if SignalCheck doesn't "see" a Serving Cell, it displays nothing. Does the Serving Cell change as you move around? If you know where a tower is, try driving around it.. see if the last two digits change from 01 to 02 to 03. Any gurus know if the "01A1B103" in the screenshot is a valid LTE cell ID, whether in a live market or possibly set for testing? It has been stated several times (including just a few days ago, a few posts up) by knowledgeable folks on here that the EVO cannot be connected to EV-DO and LTE at the same time.. but I wonder if it can "see" both at the same time if it's being prevented from connecting to one of them? This happens to me too sometimes. My EVO reports the connection type as LTE when it first loses its connection. Very odd, but it's not SignalCheck-related... Android briefly reports a (bogus) LTE connection right before Airplane Mode kicks in. -Mike
  9. mikejeep
    Sorry for taking so long to get back to you! When you are seeing that, are any of the LTE values changing in CDMA Field Test? Or are they holding steady? I just tested your scenario out by setting my EVO to LTE-only mode, grabbing a live LTE signal, then moving out of the signal area.. once the LTE signal is lost, it appears that CDMA Field Test does not clear out the stale data -- the last valid LTE signal information is "frozen" on the screen until another valid reading is obtained. It does not reflect when you are disconnected. So, it looks like you did find a bug... in CDMA Field Test, not SignalCheck! -Mike
  10. mikejeep
    I have not upgraded my EVO LTE to JB yet either, so I can't confirm it personally. But I have seen other threads on XDA and elsewhere talking about this exact issue, and apparently others have resolved the problem by upgrading. As far as LTE issues, each software, firmware, and radio upgrade has reportedly improved the situation. I'm running ICS with thte latest firmware and radio, and while I still have some issues, I believe a lot of it is related to the half-built LTE network in my area. If you want to update your device the easy way (or your device is not rooted), take all of the latest stock Sprint updates, and you'll be on JB with the latest radios and firmware. If you don't want to upgrade to JB yet, you can still install the latest firmware and radios if your device is fully rooted (S-OFF) and you can follow directions.. check the links below for more information on that, there are instructions and a lengthy discussion: http://forum.xda-dev....php?p=27266927 http://themikmik.com...-3-16-651-3-OTA If you don't feel comfortable following the instructions there, or your device is not fully rooted, don't try it. You could brick (i.e. break/crash/wreck/render inoperable) your device if you do it wrong. If you have questions about this process, check those threads; most of the questions you might have are probably already answered. -Mike
  11. mikejeep
    I have not had any time to finish up the next release or reply to every support issue over the past week.. sorry! Life gets in the way sometimes. Just need a little more time. Still testing the CM10.1 bugfixes, hopefully I can polish that off over the weekend. I always make sure to keep up with the thread, even if I don't have time to respond.. I will be in touch with each of you when I have an update or troubleshooting questions. -Mike
  12. mikejeep
    AJ, digiblur, or any of the many others reading this that are more knowledgeable than me.. From what I can find online, it looks like the valid range of LTE RSRQ is -19.5 to -3. Is that accurate? Most of the false LTE reports I am seeing show -20 RSRQ, so I thought that could be a useful indicator of an invalid reading. However, on my stock EVO LTE, I'm seeing -20 RSRQ several times per minute while on an active LTE connection with decent (-90ish) RSRP... -Mike
  13. mikejeep
    Thanks to all for their screenshots and feedback posted here or sent to me directly! It has been very helpful in narrowing down the problem. It appears to be isolated to those running nightly builds of CM10.1. There are known issues with LTE signal strength calculations on those builds. I am testing a fix that will resolve many of these issues in SignalCheck; I intend to have it released by tonight. In the meantime, if you don't see "LTE" as your connection type, any LTE signal data you are seeing is probably invalid. Is anyone experiencing any "odd" LTE data on a non-nightly CM10 build (like an M-release)? I have not had any such reports, but I know many people prefer the nightlies. The CM folks don't really accept bug reports on the nightlies because (understandably) they are essentially beta versions for testing purposes. -Mike
  14. mikejeep
    John, Your screen shot has inadvertantly helped confirm a bug I have started to hear reports of. The latest CM10.1 builds (those with Android 4.2.x) are reporting incorrect LTE values. Many people are seeing false readings (usually with values identical to what you had showing, so that's probably what you were experiencing), and when you do have a "legitimate" LTE connection, the asu values are out of whack. Do you see LTE appear in SignalCheck often, and when you do (but are still showing eHRPD or EV-DO connection), do the LTE values stay steady? I'm going to get in touch with the CM devs to see what might have changed in the latest builds. Until then, any LTE values that seem odd on CM10 (especially when your device is not reporting an LTE connection) are probably incorrect. -Mike
  15. mikejeep
    Hi Lee, sorry for not replying sooner. I have the same device and never experienced that problem, nor have I received any reports of similar behavior. I have a zillion questions for you; I'll reply here for the benefit of everyone else, but feel free to PM me if you prefer. What ROM, what version of Android, and what version of SignalCheck are you running? What do you mean by "the new menu appears"? Are you running any task-killer (aka "memory optimizer") apps or anything similar? How long have you been having this problem? Did you recently upgrade any device firmware/software/etc? If you reboot your device, does the problem come back? Thanks, -Mike
  16. mikejeep
    The Cell ID is what the site is broadcasting.. it does not directly correlate to the ID listed on Robert's maps as far as I know. Others have discovered that the ID breaks down to market + site + sector.. the last two digits being the sector (01/02/03). -Mike
  17. mikejeep
    I had tried the latest CM10.1 as well; I have LTE at home near a window facing a hilltop tower, so its a great testing ground for 3G, 4G, and handoffs. When I was connected to LTE, CM reported the same bogus MAX_INT values you saw. (So technically, it was populated, just not with anything useful.) Hopefully, new devices with JB from the beginning will utilize the API better.. -Mike
  18. mikejeep
    Agreed! Hopefully it's just weather-related.. I figured it would slow down a bit because of that. This started off as one of the strongest NV markets once the ball started rolling, but progress seems to have trailed off. The active 4G sites near me came within the first few weeks, and haven't had any since. Tons of 3G sites near me have been done for quite awhile, come on backhaul! -Mike
  19. mikejeep
    It depends on where you are.. the latitude/longitude is set by the provider. Sometimes it is the exact location of the site, other times it is offset some distance from the site, and some sites do not broadcast any location information at all. For example, in my area I know that Sprint sites are offset, and Verizon sites do not show any location at all. The app takes the latitude/longitude being broadcast and geocodes it using a Google server to determine the street address. If its not near a roadway or landmark, it will give a more general location such as the city and state. I am in the early stages of trying out a mapping component to record where you connect to various sites, with the goal of creating a usable set of data points to calculate where a tower might be and what the different IDs are. One purpose could be to make it easier to cross reference what you are connecting to with Robert's sponsor maps. -Mike
  20. mikejeep
    Are you syncing your contacts through Facebook at all? A glitch popped up a few months ago (I'm suffering from it myself) and most indications are that its related to Facebook contacts sync. Supposedly the issue is fixed in Jelly Bean. -Mike
  21. mikejeep
    I saw the comments on Google Play about Netmonitor being a "dangerous" app, but having frequently used it for over a year, I can say I've never seen any indications that it harmed anything on any of my phones. One of the last few Netmonitor updates did break the geocoding. Even though Sprint sites in my area broadcast the sector offset location instead of the tower location, it was always accurate. Now, as someone else pointed out, the map still appears correct, but the text description of the address is off by thousands of miles. I tried contacting the developer several times without any response. So, I decided to put the geocoding feature into my own app instead, and it works like a charm -Mike
  22. mikejeep
    The Lite (free) version has been updated on Google Play and should be available within an hour or so. Also, I accidentally neglected to give a huge thank you to lordsutch for allowing me to use some of his code, which was the core of the new LTE Cell ID capabilities for HTC devices. Without his work, that would not be in this update. Thank you!! -Mike
  23. mikejeep
    Still working on the ringtone selection.. it's at the top of my list. There is a bug in Android preventing the "normal" way to choose a tone from working correctly, so I have been trying to come up with my own workaround. Does the other LTE data appear to be correct? Does anyone else see odd values for asu? -Mike
  24. mikejeep
    Haha wow I can't sneak anything past you guys.. updated app and posted a screen shot before I could even get the word out that it was available! Love it.. -Mike
  25. mikejeep
    Version 3.03 has been released.. Pro is available now, Lite should be online by tonight. Most HTC users on stock ROMs should see LTE cell IDs in the new release.. perhaps custom ROMs too, but not positive. Pro users will see a new option to show the street address of the 1X site they are connected to. As discussed before, the location information is provided by the carrier, and varies in accuracy. With Sprint, you're usually going to get a point some distance from the tower that correlates to the sector. With Verizon, you probably won't get any address at all. Others might get the exact location of the tower. Let me know if you find any bugs.. -Mike
×
×
  • Create New...