Jump to content

SpenceSouth

S4GRU Premier Sponsor
  • Posts

    1,846
  • Joined

  • Last visited

Everything posted by SpenceSouth

  1. Well it still shouldn't crash... I am probably not handling a null value somewhere a long the lines. That particular part of the application gets very complicated.
  2. What phone model is that? Can you try to start it again and then after it force closes go back to the map tab right away and press the Export Logcat button in the menu? That'll copy the logcat into a text file in /maptacular/ that you will be able to send me. Once I have that I should be able to figure out what's going wrong pretty quickly. Sent from my Nexus 5 using Tapatalk
  3. Same here as well. The dBm "may" be inflated but the effects of having a stronger signal reading are real. Sent from my Nexus 5 using Tapatalk
  4. No kidding there. Not that I'd ever switch but sometimes it kind of makes you envy Apple's one device model system. Thanks! Sent from my Nexus 5 using Tapatalk
  5. Yeah, even though your G3 is showing a correct PLMN ID in engineering screen the system API's we both use are likely reporting incorrect info. I'd start by reporting it to LG... We might be able to find a work around for this eventually. Sent from my Nexus 5 using Tapatalk
  6. Took an hour trip down I-4 and the query algorithms have done a great job separating the distinct bands and sites out of the 120 logs. Sent from my Nexus 5 using Tapatalk
  7. I didn't get a lot of beta feedback and upgraded A LOT of features so it is on a pretty slow rollout through out the week. 100% of users should have it by Thursday, but if you think you might want to be an active beta user you can PM me and I'll send you a link to request access at. The beta group has access to the same public version that everyone else does (as of right now) but you would be able to get it tonight.
  8. Wow I haven't realized how long it has been since I have posted here. As of today the latest version of LTE Discovery is on the market (v3.7) which is slowly going to be rolling out over the next few days due to the size and scope of the update. Notable new features: 1. Advanced Visual 1x Logger- The advanced visual 1x logger is a small part of a much larger project I have been working on. However since it took so long to make this part I felt that it should be released and enjoyed now rather than later. The premise of the logger is that it will identify, triangulate, and combine 1x800 and 1x1900 signals and towers into a single tower icon on the map. I've found that the location algorithms I have created have seemed to be nearly spot on from the regularly reported systems values when the app has mapped three sectors so I am excited to see how this works out for everyone else. 2. EARFCN card- Thought this was something that was sorely needed since people have a lot of questions on EARFCN channels. Simply put this card will show the projected EARFCN range. The flip side of the card (pro version click) will allow users to calculate the frequency and band of EARFCN DL and UP channels. There is also a check shortcut that can bring users into their debug or service screens to check their EARFCN values, but the methods it supports are very limited at the moment. 3. Fixed GPS Log- This one has been a long time coming... I have finally fixed the GPS Log and rebranded it as the LTE Log since there is a dedicated 1x logger as well. The LTE Log screen shows all the sites you have detected. There is a new LTE Log card addition that has automated queries as you log sites. Basically it will show you the unique number of sites you have connected to and the unique number of band occurrences (not to be confused with total). It is actually an amazingly useful feature to have and allows you to learn a lot of about the state of the LTE network around you at a glance. The number of automated queries are limited to three on devices that fully report data and there are more planned on the way. 4. Live Band Indicators- I have added some well styled band icons to the live notification. Again the idea is to allow users to get an idea of their current network at a glance and this has worked remarkably well in testing as well. Well that's the list! I hope you guys enjoy the update. I have been working on it with my partner Dan for over a month and a half now nearly full time. It feels great to finally be done and get people using it. This is a VERY large update that touches on many core parts of the application so I won't be surprised to find a few bugs here and there. If you find one please report it to me so I can get it fixed quickly. Also if you absolutely cannot wait to get the update you can request to join the beta group to get instant access. (Not the best staged images as they are all from the beta development stages, but you'll get the gist of it)
  9. I've noticed something similar in Orlando over the past week. Finally got B41 again today. Sent from my Nexus 5 using Tapatalk
  10. I haven't heard of anyone having issues with seeing B41 or with B41 alerts on LTE Discovery so you should be able to find it with it. If that isn't the case just shoot me a message and I'll get it fixed. Sent from my Nexus 5 using Tapatalk
  11. I think they may have just begun optimizing the B26 sites in Orlando. I noticed that from the Avalon Park site I had a -82dBm signal on B26 and then a -97dBm signal from B25 on the same site. Sent from my Nexus 5 using Tapatalk
  12. Glad I could help! Sent from my Nexus 5 using Tapatalk
  13. From other sources the issue seems to be largely related to an IPv6 bug. Since T-Mobile has the option of sending texts via IPv4 those users haven't seen the issue as much.
  14. Some people, including myself, were having MMS issues. Messages would never download and couldn't send. Sent from my Nexus 5 using Tapatalk
  15. I had much better battery life on it as well. I switched back to 4.4.4 because I have to test apps on KitKat and the lack of MMS was getting annoying. I hated the new notification system so there was that too... Sent from my Nexus 5 using Tapatalk
  16. If SignalCheck doesn't show GCI info it's because Motorola doesn't allow access to the needed API or doesn't report GCI properly. You may be out of luck until you upgrade your phone. Sent from my Nexus 5 using Tapatalk
  17. Great I'll give Sprint a call later today. Thanks for the heads up!
  18. Hmmm I'll have to look into this some more! What do you know about it?
  19. Working perfectly. If you were waiting to buy it, go for it. I can personally confirm that B41, B26, and B25 all function as they should and can seamlessly switch between bands without interruption. (YMMV depending on how complete your market it, but no limitations due to the N5)
  20. I'd join, but as an existing customers I can't join other Framily's -_-
  21. I've noticed it as being marginally better. Can't wait to see it optimized. Surprisingly even on low power it does already help!
×
×
  • Create New...