mikejeep

I got it, thanks for trying to help out! Unfortunately it doesn't include logcat output. Great idea though, hadn't thought to include that somehow.. I will have to look into adding that. -Mike

Thanks for the update! If anyone wants to grab any pertinent logcat output that displays when you launch those screens from the dialer, it might help me get it going. -Mike

I know there is an argument against screen protectors, and Zagg's models, but I have been using their HD series for a couple of years. I hit up their mall kiosk and they put it on for me, and they replace it whenever I want. They don't usually charge me for the replacement if the old one is a mess. -Mike

I think the functions that query the provider database throw all errors to logcat, so if anyone sees the behavior and can catch the logcat message, please let me know. A lot of the database stuff is finicky but very tweakable. Unrelated note: Can anyone with an LG G2 confirm if the new system shortcuts added in 4.19 work correctly? -Mike

Nice screen shot collage there, thanks! Hmm.. that's new. Are you on 4.19? Are you able to see any logcat messages? -Mike

Poor digiblur.. now that it's fixed, he will be back to unusable LTE speeds. Talk about an unselfish move! -Mike

Has anyone had issues with calls going directly to voicemail while their N5 is connected to LTE? I use Google Voice for voicemail only. When I am home, I have a solid (usually around -90 dB) LTE signal. I have received many calls while at home, but a handful have gone directly to voicemail when I know the phone was connected to a strong signal and I wasn't on a call. It just happened again about a half hour ago, but a few minutes after that, I received a call without any problems, and I was sitting in the same spot with the same signal level. Time of day and day of week do not appear to be relevant, and there hasn't been any work on the towers in my area in several months. Now that I think of it, it's happened when I was out and about as well, in known accepted and "good" LTE signal areas. Anyone else seeing this? -Mike

Users in the LG G2 thread are reporting if you keep forcing PRL updates, it hops back and forth between 60657 and 55017. I am guessing that someone hit the wrong button at Sprint and 60657 wasn't supposed to be dug up from the archives and pushed out. My Nexus 5 was on 55016 and went to 55017 when I forced an update. Tried forcing an update several more times and it kept saying "No update available". -Mike

You kind of answered your own question here.. the time zone is set by the tower, and that tower is configured incorrectly. You can try contacting Sprint to let them know, but in the meantime you would have to disable the option to have the network set your time zone if you want it to stop until they fix it. -Mike

Pretty sure that was a spam bot... -Mike

You should start peddling non-LTE PRLs to all of your friends and neighbors down there, soon enough you'll have the entire network to yourself! -Mike

You can use SignalCheck or another app to put up a notification icon showing your voice signal. Other than that, you would need custom tweaks to SystemUI.apk to edit the system bars. -Mike

I blame my wife. I was completely normal until 3 months ago, I swear.. -Mike

Ha!! I knew that didn't sound right.. yep, it was the TP2. That's why you should sleep at 5am, not go S4GRUing. I still miss my physical keyboard! -Mike

I just remembered that when I deactivated my EVO LTE, a "Data Call Failure" warning prompt constantly kept popping up. Go into Settings and disable Mobile Data; that will prevent the message from appearing. It will not affect the signals that SignalCheck sees, it just prevents the phone from trying to authenticate a data session with the network. -Mike

Well that's not really funny business.. prior to Android 4.2, there was no standard Android routine to get the LTE cell identity. So to get it, you need an alternate method, like SignalCheck uses to get it on HTC devices. Unfortunately, other manufacturers do not make access to this data very easy, and Samsung has security measures in place that complicate things even further. Making things worse, Samsung has been slow to add "standard" support in their devices running Android 4.2. I'm still working on it though, because I know how valuable that data would be for my Samsung users. Until last month, Samsung and HTC devices were by far the most popular among SignalCheck users. Now the Nexus 5 and G2 have exploded onto the stat sheet, so I am trying to add more support for LG devices, but I am not abandoning my Samsung efforts. -Mike

Man, you're old. I think I was only 30 when that went down.. ah, memories. I remember rooting my EVO Shift (a Windows phone for those of you unfamiliar) to get a hacked-together version of Froyo on it. Even with its limited functionality, I remember thinking it was exactly what I hoped to see on phones someday. Still love it, many desserts later. I have no problem supporting older devices, at least for now. They are actually easier, manufacturers didn't try as much funny business behind the scenes back then, and there was none of this crazy new-fangled LTE stuff to worry about! -Mike

Received mine today as well, fits perfectly, exactly the same solid quality as their cases for other devices, no impact on RF. Accommodates all of the USB cords I have tested; the Cruzerlite TPU cases failed that test for me. I wish Seidio offered a version without a kickstand I will never use, but I'll get used to holding it. I had a Surface on my EVO for a year and a half and loved it. -Mike

No worries.. the app does not care who the wireless provider is, it will work on any device running Android 2.2 or newer. There is also an older version for Android 2.1, but it does not have as many features and will not receive any updates. You already noted the one drawback for Verizon users.. other than that, everything else should work fine. And if Verizon changes their mind someday, SignalCheck will start showing a BSL for them too -Mike

If you are updating from 4.4.1, you probably don't need to revert anything because the changes are minimal. Give it a try.. worst-case scenario, you will get an error message; it doesn't cause any harm. If it fails, then you likely just need to flash the stock system.img first. -Mike

Not in SignalCheck, my friend -Mike

Actually I think I do recall you mentioning that bug shortly after I had noticed it myself. The only reason it slipped through the cracks on my end was because I didn't have a non-CDMA LTE device to test with. Nexus 5 FTW! -Mike

I believe that outline-style icon means the microphone is not actively listening for voice commands. When the icon is solid, it is actively listening. Perhaps you disabled it, or something else shut it off automatically, maybe low battery? (Just a guess there, no idea if it would do that.) -Mike

SignalCheck actually doesn't do anything specific to deactivated phones; they continue to receive a signal, so the app reports it. It ignores whether or not any data can be transmitted or received. You should not have to "do" anything to the EVO. Perhaps move them a few inches apart if it's interfering while you are trying to watch the signal levels? That wouldn't have anything to do with the app, just typical RF behavior.. -Mike

SignalCheck Pro has been updated! Version 4.19 has been pushed out to Google Play and should be available shortly. Here is a link. There are many changes.. here is the full changelog with explanations: Added display of mobile data connection status and mobile data traffic activity to action bar. This is the most noticeable change in this version; you will now see if your mobile data connection (not wi-fi) is active, and if so, if any data is currently flowing. This field is displayed in green if the connection is active, and red if it is not, providing a way to easily see the status of your connection at a quick glance. Added Android 4.0-style action bar for devices running older OS versions. Allows older devices to see the mobile data connection status and traffic display mentioned above. An unfortunate side effect of this is an increased APK size, but it's still only about 974 KB. Changed secondary status bar icon behavior; if only an LTE connection is active, secondary 1X or GSM icon will be hidden, regardless of preference setting. (Pro) Those of us with newer non-SVLTE devices will appreciate this unnecessary nuisance disappearing! Changed system shortcut menu options and expanded support for HTC, LG, and Samsung devices; menu options are no longer manufacturer-specific. (Pro) Made some more progress with the screens usually accessed by dialer codes, and organized them in a better manner. Samsung users are now sent directly to the Data and Debug screens. If these menus do not work on your device, feel free to ask and I can try adding support (or explain why I can't). Added feature providing users with the ability to send a diagnostic report for technical support. This can be found in the app under About SignalCheck > Send Diagnostics. If you are experiencing an issue with the app, it provides a spot to describe the problem and send technical information directly to me. None of the technical information identifies your specific device. Resolved issue with missing/invalid EV-DO provider name in the notification pulldown. (Pro) The EV-DO/eHRPD provider name was vanishing from the notification pulldown screen.. this should fix it. On non-HTC devices, this is always going to display the 1X provider, as there is no way to get the true provider name right now. Improved reliability of Reset Data Connection feature. (Pro) It still requires root permissions on devices running Android 4.2 or newer, but it should work a little better now. Non-rooted users will see an error message explaining why it didn't work. Resolved issue with false GSM connections appearing with static data. Nobody ever reported this to me, but most GSM devices were reporting a steady -85 dB GSM signal when connected to LTE. This was a bug.. surprised nobody ever mentioned it. Overhauled main GSM screen; section(s) will now display the type of connection. Inactive connections will now be hidden. Simplifying and cleaning up things on the non-CDMA side of things. Removed routine to disable CDMA-only preferences on GSM devices. All options are now visible for all devices; CDMA-only features will have no effect on GSM devices, and GSM features will have no effect on CDMA devices. (Pro) Some users were seeing app preferences being changed without their input. Changed “Carrier” label to “Provider” for clarity and standardization Changed display of “UMTS” to “W-CDMA” for clarity and standardization. Just trying to keep things technically correct.. thank you AJ. Removed widget action options that are still in testing. (Pro) Just forgot to hide some options from the last test version. Selecting them wouldn't have hurt anything. Resolved issue with missing provider name for some Samsung LTE users. More fixes for the 31000/310000 LTE bug on Samsung devices. Updated a small number of Cricket entries in the CDMA provider database. Not much else I can say about this. SignalCheck Lite (free) will be updated sometime next week. Thank you as always for all the support, especially to those of you who have been helping to squash bugs and test new features -- I appreciate it! -Mike