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
    Yep, send info for anything you've got! -Mike
  2. mikejeep
    SignalCheck Pro has been updated! Version 4.22 should be available on Google Play shortly. Here is the changelog: Added workaround for Android 4.4+ bug which stops icon and widget updates; KitKat devices now require the main status bar icon to be enabled until another solution is found. (Pro) This is the main reason for this update. Testing indicates the issues appear to be resolved, including if you clear SignalCheck from the Recent Apps screen. The mandatory icon may change in the future, depending on how Google handles the bug. Please holler if you experience any problems. Resolved issue with no connection showing when in LTE-only mode. Changed 1X and eHRPD/EV-DO sections to indicate “Disabled” when in LTE-only mode. This should be useful for a lot of users on here and might help show Band 41 connections that were previously not appearing in the app. Added release date to About screen. Happy New Year! Added Samsung “Hidden Menu” back to System Shortcuts. (Pro) Some Samsung phones do not work well with the standard shortcuts, so the previous method is back as another menu option. Resolved issue with force closes when connecting to LTE in certain situations. Some users experienced some freezing/crashing problems, this should now be resolved. Updated provider database. Corrections to some international providers. As usual, Lite users will get their update in about a week. Thank you once again to everyone.. SignalCheck was released one year ago this week.. never imagined it would ever have over 28,000 total downloads, let alone in the first year! -Mike
  3. mikejeep
    I made what appears to be some reasonable progress with Samsung support earlier tonight.. they opened a ticket for the incorrect LTE MCC-MNC ID (the S4T always shows 310120) and missing GCI/PCI/TAC on the S4T. Now that I have my foot in the door, I would like to try making some progress with the two biggest issues on their other devices. I need help from Samsung users to collect some data to pass along. Please e-mail me if you have a Samsung device other than the S4T that is experiencing either of the following issues on a stock ROM (EDIT: or a custom ROM that is based off stock), even if you have previously reported it to me: Incorrect LTE MCC-MNC (i.e. 31000/310000) on any Android version Missing LTE GCI/PCI on Android 4.2 or newer Use this link to e-mail me with a pre-filled template, or send it to support-at-bluelinepc-dot-com with something like "Samsung baseband bug" as the subject, and include the following info: Which bug (or both) you are experiencing Model (i.e. SPH-L720; grab it from Settings > About phone) Mobile provider (i.e. Sprint) Baseband version (from Settings > About phone) Android version (i.e. 4.2.2) I have no idea how seriously they will take me, but it can't hurt to try. HTC has been surprisingly receptive, so perhaps the right folks at Samsung will be as well. Thanks, -Mike
  4. mikejeep
    Only if you have SuperSU (or similar app) configured that way.. I have it turned off myself. In SuperSU, it's under Settings > Re-authentication. -Mike
  5. mikejeep
    I think I missed this message from last week, sorry! First of all, quality video, never thought I'd see SignalCheck put on YouTube with a soundtrack, LOL.. as far as your issue goes, I notice the same thing as well. It's an unfortunate side effect of needing a custom root-only method to reset the radio on 4.2+ devices. Differences in how SU programs grant or prompt access make it tricky to have something like this working perfectly. The app is simply requesting root access and then executing a command, nothing that should have a long delay or cause crashes.. but it does, especially on the first try or if you prefer to prompt for root access. I have a lot of other things ahead of it on the priority list, but I have tried tweaking it a few times to improve performance. I am still hopeful that Google will re-allow developers to control the radio in a future version, like they did prior to 4.2. The best workaround I can suggest is to auto-grant SignalCheck root access in SuperSU or whatever you might be using, without prompting.. that seems to work the best for me. -Mike
  6. mikejeep
    They knew Josh would buy it if they put that in there! -Mike
  7. mikejeep
    Yes I believe this is going to be a significant problem if Google does not address it quickly. Last night I finally came up with a workaround for SignalCheck, it's in testing now. As long as no issues come up during testing, it will be released soon. -Mike
  8. mikejeep
    As far as SignalCheck goes, I have some disappointing news.. unless Tim's phone is unique, it looks like Samsung is still not reporting any 'extra' LTE data, such as GCI, PCI, and TAC. I had high hopes that this specific device would change that, but that is not the case, at least not on the initial release. More disturbing is that it also reports 310-120 to Android even when the enginerring screen (can't believe they haven't fixed that yet either) says 311-490. I've never been able to get in contact with anyone useful at Samsung, but I'm going to make a push tomorrow to bark up the right tree. The incorrect MCC-MNC reporting is going to goof up other things besides my cute little app. -Mike
  9. mikejeep
    Major highways usually have good coverage, but the reason it is so pronounced on Sensorly is because that's where the most users of the app are traveling. You might be the only person who maps your neighborhood, but a lot more people are traveling through town on the big road. -Mike
  10. mikejeep
    I love that you haven't taken the factory screen wrap off the N5 yet, but it's already running SignalCheck Pro, haha! -Mike
  11. mikejeep
    SignalCheck Lite (free version) has finally been upgraded.. version 4.21L should be available on Google Play shortly. Sorry it took so long! It includes all of the relevant changes that were included in 4.19 but never released as a Lite version. It is a significant upgrade from version 4.18. Full changelog for both versions is here: http://www.bluelinepc.com/signalcheck/change-log/ Happy New Year! -Mike
  12. mikejeep
    I looked into it more tonight, and figured out what was going on, at least at the software level. On the Nexus 5, Android is reporting an LTE connection and valid signal data; however, it is also reporting the telephony service state as "out of service". This is what leads SignalCheck (and probably the stock notification pulldown) to believe that there is no connection. I wonder if the service state is indicating the voice service state, not the overall mobile service state. I'm digging around for answers and trying to see what I can tweak on my end. -Mike
  13. mikejeep

    LG G2 Users Thread!

    mikejeep replied to koiulpoi's topic in LG

    Google removed developer access to the radio starting in Android 4.2. Any 4.2+ device needs to be rooted in order to use the alternative Reset Data Connection feature I implemented. Unfortunately, this will not change unless Google changes their mind and opens up access again somehow. Keep an eye on the thread in my signature for more. -Mike
  14. mikejeep
    You might be running into issues because Adobe stopped supporting Flash on Android 4.1+. Chrome and many stock browsers will not show any Flash content, which many websites use to display video. I believe there are third-party browsers out there that include Flash support, but I haven't tried any of them. -Mike
  15. mikejeep
    FYI, SignalCheck might not need mobile location services to work properly -- it varies by device. I changed the warning prompt in the latest version to reflect this. If you prefer to keep your location services disabled, try using the app and see if it works properly. The most common problem is you will not see any 1xRTT data at all, or you may see SID/NID/BID values of -1. My app doesn't actually do anything with the location, but some ROMs block access to the 1X cellular information if mobile location services are disabled. -Mike
  16. mikejeep
    Nope, no updates on my end.. I have been using LTE-only mode since I posted earlier and even after resetting the connection numerous times, it still fails to report the network type on mine. Are you sure you're in LTE-only mode on the Radio Info screen? -Mike
  17. mikejeep
    I just tried it myself.. weird! I've seen reports of this but didn't have it tied to LTE-only mode. If you look in your notification pulldown, the phone says "Searching for service" as well. The signal strength is being reported to Android (in SignalCheck, go to Preferences > General Settings > Show Hidden Data to see it), but the connection type is not. That's why the pulldown says searching and SignalCheck says "Connecting..". -Mike
  18. mikejeep
    Sprint is not releasing the software update to officially enable the "Spark" connectivity on some devices, including the G2, until early 2014. Some people have been able to intermittently connect anyway, but typically only if they cannot pick up a band 25 signal. -Mike
  19. mikejeep
    Glad to hear that the app is improving on the Band 41 front, but I think that Band 26/41 connections should be considered extraordinary on the G2 and N5 until Sprint pushes out the software update to officially allow connections. There is obviously some unfinished business behind-the-scenes. Logging is one of the most often requested features for me to add, and I have every intention of doing so. I am working on a re-design of the app that will include logging; I am trying to hold off until I can introduce that new layout. However, that layout is taking a lot longer than I expected to get working, so I am considering adding logging sooner. I do understand how useful it will be.. I want it for myself too! It's not a simple addition, but I'm actively working on it. -Mike
  20. mikejeep
    I have been researching this issue, and it now appears that there is another bug similar to the Android 4.4 problem I mentioned earlier. Not only are services being killed and not restarted automatically when an associated app is cleared from the Recent Apps list, but in 4.4.2 other services are failing to restart as well, without any interaction with the Recent Apps list. It does not appear that this issue exists in the initial version of KitKat (4.4) except when a user clears an app from Recent Apps. This is going to be a significant problem for a lot more apps than SignalCheck. It looks like as more KitKat devices are hitting the street, the full extent of the problem is being discovered. There has yet to be an official response from any Android folks. Some third-party developers have put together temporary workarounds, so I'm going to see what I can do to circumvent this. It will be a couple of days before I will be able to have anything to test. Interestingly, I have not seen this problem on my N5 on ART; in fact, I have seen the SignalCheck service restart itself after it has been killed due to low resources. If anyone is interested, the relevant Android bug tickets are #63618 and #63793; feel free 'star' them to help prioritize the problem. -Mike
  21. mikejeep
    I guess you are your own special Spark.. Sometimes these engineering screens make me wonder.. Samsung especially.. they can't even correctly spell engineering! Next time you see 311490, hit About > Send Diagnostics if you don't mind. I feel like you've sent me a report already but I can't seem to find it. -Mike
  22. mikejeep
    Hmm... that pretty much makes the icons & widget useless, sorry it's misbehaving! It does sound like there is still something outside of the app killing off the background service.. is your widget showing stale values, or is it a blank gray square? Just to confirm one more time, you are not clearing SignalCheck from the Recent Apps list, correct? The Android system is only supposed to kill services like SignalCheck when system resources get low, and should restart them automatically once enough resources are available again. Turning off the screen should not trigger this. And the N5 has plenty of memory to handle my relatively puny service. I've been using ART on my N5 for a few weeks and have not seen any adverse affects on SignalCheck. But, if you are bored and have a chunk of spare time to wait for the cache to rebuild and want to try switching back to dalvik to see if it helps, let me know what happens. Right now, I do not believe ART is the culprit. I am working on an update for you to try out, hopefully it will provide some more insight into what's causing this. I will keep you posted. -Mike
  23. mikejeep
    The 4.4.1 and 4.4.2 updates include several nice fixes including a huge speaker volume improvement. Update to 4.4.2 before rooting, because you will have to do it over again anyway. -Mike
  24. mikejeep

    LG G2 Users Thread!

    mikejeep replied to koiulpoi's topic in LG

    How long were you offline between your old and new G2's? It could have been a bad device, but keep in mind it might also be a result of NV upgrade progress in your area. -Mike
  25. mikejeep
    Well that's certainly annoying! Until AJ mentioned it the other day, nobody had reported this. Do either of you know how long this has been happening? Do you use the widget as well, and if so, does that disappear too? Any custom launchers in play? So far I have been unable to find anything on my end that would cause that. I found a vague uncredited reference mentioning that if an app is running while it is updated, the icon may disappear, but I am always running it, and have never seen this behavior on any of the devices I use for testing. -Mike
×
×
  • Create New...