Jump to content

SpenceSouth

S4GRU Premier Sponsor
  • Posts

    1,846
  • Joined

  • Last visited

Posts posted by SpenceSouth

  1. OMG yes.. I had to uninstall it because it was crashing the whole phone! 

     

    If it wouldn't be any trouble, could you help me troubleshoot the problem so I can get it fixed?  Did this just happen on the very last update?

  2. I'm happy to report that the B41 issue is no longer present. The map function works flawlessly as do the live notifications! Over all, great work!

     

    I have seen the app hang a little while logging.

     

    Sent from my LG G3 using Tapatalk

    Great glad to hear it!

     

    Yeah I've noticed some lag myself. A tune up is definitely on the schedule.

     

    Sent from my Nexus 5 using Tapatalk

    • Like 3
  3. Got it! Thanks! I've only spent a few minutes with the beta version so far, but the map functionality works much better now! I'll play with it more tomorrow.

     

    Thanks again!

     

    Sent from my LG G3 using Tapatalk

    The beta should have the B41 fix to the problem you have been seeing as well.

     

    Sent from my Nexus 5 using Tapatalk

  4. Awesome!!! If you need a beta tester for the G3, that's also in Jax, let me know.

     

    Sent from my LG G3 using Tapatalk

    Could always use more beta testers. Feel free to request access to the group and I'll add you.

     

    bit.ly/ltebeta

     

    Sent from my Nexus 5 using Tapatalk

  5. Ignore the random line... Still working the kinks out of this beta version. I used the app to monitor my drive from Orlando to Jax and observed something pretty interesting. My phone only dropped down to 3G six times during the two and a half hour drive. That's how solid Sprints LTE coverage is in Florida now. It was a solid mix of B25 and B26 the entire way up.

     

    huqupy4e.jpg

     

    Sent from my Nexus 5 using Tapatalk

    • Like 1
  6. It's showing a -1 for band here on a standard band 17 site.

    What's nice about how I setup the logs is once I correct the bug the app will correct anywhere the -1 was recorded under those conditions. I'll have to myself a pat on the back for thinking ahead about that one.

     

    Sent from my Nexus 5 using Tapatalk

    • Like 1
  7. Is that place any good? They're building one in my city. I've never eaten at Five Guys. But everyone is going nuts about how good it is.

     

    Robert via Samsung Note 8.0 using Tapatalk Pro

     

    No, there's nothing good about Five Guys at all.  They are GREAT.  If you want some consistently great burgers and fries then I'd highly recommend you give them a try.  I have never been to Five Guys and left unsatisfied.

     

    The find success in keeping their process very simple.  Your food comes in a brown paper bag, your burgers are wrapped in foil, the burgers are always made as you order, and the fries always come right out of the bat and into your bag hot.

    • Like 3
  8. There was a sprint user who claims to have got it working by flashing an old radio and a couple other things over in the XDA thread but I had already switched back so can't confirm.

     

    Sent from my Nexus 5 using Tapatalk

    Well that's good news. Thanks for the heads up, I might take a second crack at Android L and see if the fix is legit or not.

     

    Sent from my Nexus 5 using Tapatalk

  9. Ah, that is an interesting idea.. although I would have to do some work to make sure I can add those columns to existing database files without corrupting them. I'll put that as a priority to work on.

     

    I do want to apologize to everyone for my lack of any updates lately.. I have been absolutely swamped at work, which is sucking away all the free time I need to work on my master's.. leaving less than no time for SignalCheck. :( I'm still trying to find exactly what is crashing Android L, I wanted to at least get that out; I might just push an update that disables all notifications if it detects Android L as a temporary fix, since that would be quicker.

     

     

    As Flompholph pointed out, that is just a placeholder, and there is a known Android bug that causes the address geocoder to randomly stop working, and requires a reboot to get going again. You might have been seeing the address "right away" in the other areas because the app had previously cached them (which circumvents that bug nicely and does not use any data transfer).

     

     

    This issue has been my nemesis since B26 and B41 started lighting up, and I'm seeing others report it to SpenceSouth and the LTE Discovery crew in their app, so I know it's not just me. For some reason, phones are not always reporting the same PLMN to the engineering screen and to the OS. For a long time I thought it was a bug in my code that runs if the PLMN changes, but now that I'm seeing similar issues with other apps, it makes more sense. It appears to be very random as to when it does or does not report the same values. Sadly I would expect the N5 to be the most well-behaved, but it seems to suffer from the same issues that other devices do. I don't know if it's a network issue, an Android bug, an engineering screen bug, or lousy programming in the radio firmware. I'm still looking for solutions but it's really just a case of the device feeding the app (or the engineering screens) bad data.

     

    -Mike

    My issue seemed to be less of the system reporting erroneous data and more of me just not properly handling the PLMN ID as it switched between B41 and B25/B26 sites (which fortunately wasn't a bad fix).  I don't know how you handle the data as you check for B41, but from what I have seen of SignalCheck screenshots it seems that it is always 311490 that is reported instead of 311870 when that bug pops up... Do you pull the PLMN ID value directly from the system, or is there a chance you may be inadvertently returning the same constant string during your check?

     

    I don't know if that helps or not, but feel free to bounce ideas off of me if you need to.

  10. Still occasionally having an issue with reporting B41 as B25. In the log it is showing B41, as is the engineering screen. But the app is reporting it as B25.

     

     

    Also, when on 3G, the tower is reporting its coordinance, but I cant get it to show-up on the map. This has been happening since the last update.

     

    Keep up the good work! Love the app!

     

    Sent from my LG G3 using Tapatalk

     

    Could you tell me if the band notification icons from Live Mode in the Discover tab is scaling okay on the G3?  Sorry to bug you with this.  You are one of the few I know with this phone lol.

  11. Still occasionally having an issue with reporting B41 as B25. In the log it is showing B41, as is the engineering screen. But the app is reporting it as B25.

     

     

    Also, when on 3G, the tower is reporting its coordinance, but I cant get it to show-up on the map. This has been happening since the last update.

     

    Keep up the good work! Love the app!

     

    Sent from my LG G3 using Tapatalk

    Thanks for these screenshots!  I know exactly what needs to be done to fix this one.  It is a similar issue to the log bug where the LTE Card is checking for band info faster than the system can accurately populate the data.  Everything time I find this as an issue I laugh a little to myself because the usual dev problem is that the code isn't running quickly enough. 

     

    I'll roll out a patch to the beta users today and maybe Booyser24 can confirm a fix for us.

     

    Does the tower still not show on the map even when 1x logging is enabled in the menu tab?  We are working on adding back the passive non-logging map functionality to users now.  In the midst of adding in much greater map functionality I kind of overlooked that until now.

    • Like 2
  12. There are only a few flagships a year. If you are reviewing that many devices, than yes it is likely you're running into the mid and low end devices, which tend to be bugger and less well made.

     

    HTC flagships have been some of the best devices out there. With the exception of the EVO 3D (which wasn't all that bad....) the HTC flagship device each year generally has been the device that sets the bar, even though they generally aren't as popular. Mainly because of marketing.

     

    If you want a device that has issues with lag, get a Samsung.

     

    :ninja:

    Completely agree with you in regards to HTC. They make great devices and they deserve to be on the top, but that sub par marketing really gets them at the end of the day.

     

    Sent from my Nexus 5 using Tapatalk

    • Like 3
×
×
  • Create New...