Jump to content

mikejeep

Honored Premier Sponsor
  • Posts

    3,264
  • Joined

  • Last visited

  • Days Won

    186

Everything posted by mikejeep

  1. I don't think anyone is "skipping out" on anything.. sites are marked as accepted after they have been inspected and approved on behalf of Sprint. You have been around here long enough to know that it is very common for sites to be live but not accepted, or accepted but not live. Not to mention that I imagine keeping these maps updated is a ridiculous amount of work for Robert, or perhaps Robert hasn't received the information for that site yet. If the site appears to be live, just enjoy it and don't worry about the map! -Mike
  2. Hmm.. Wonder if I could port that to the N5..hmm..too many Damn projects already. But what's another right? Tapatalk strikes again? -Mike
  3. Should they really be 9 A B? Or is SignalCheck just showing the wrong value? The information I have about this alternate method of identifying the sector was specific to the Boston market (but thought to be used elsewhere on Sprint's network), and proved to be correct here. -Mike
  4. Actually, I was mistaken earlier.. some deactivated devices do work ok. The Samsung Galaxy Victory that Robert loaned me is deactivated and always connects to LTE without any issues, I use it for testing nearly every day. Perhaps it doesn't try to register/authenticate/connect the same way some of the other devices do, so it never gets kicked off. -Mike
  5. I was going to suggest going to the Radio Info screen (either with Nexus 5 Field Test or SignalCheck Pro.. there is a dialer code, but I can't remember what it is) and check the band selection in there, but when I click on it, my N5 crashes. I guess you're not supposed to do that. Check the Radio Info screen anyway, ensure it's set to CDMA auto (PRL), LTE/CDMA auto (PRL), or LTE/GSM/CDMA auto (PRL). Each of those is valid on Sprint; it shouldn't effect what band you are on, but who knows. It might restart the radio and get you connected. Do you have a SIM inserted? Try removing and reseating it, then reboot. -Mike
  6. Nice write-up, thanks for sharing with us! I have a deactivated EVO LTE that will only connect to LTE briefly when I first power it up; it then falls back to EV-DO and never shows LTE (or eHRPD) again. When it was activated, I had solid LTE performance in the same place (and two other devices still on LTE in the same place no problem), so it's definitely related to activation. Sprint must block unregistered devices from connecting to LTE (or eHRPD). -Mike
  7. Cool stuff.. every time I see a shot of multi-view, I'm slightly jealous it's only a Samsung thing. Your screen shot reminded me about something I meant to share earlier. I received some information about the "Site Hint" field.. markets that don't seem to show it properly (i.e. "Sector A" instead of 1/2/3) use a different scheme, where the sector isn't the last hex digit, but instead is represented by the third digit from the right (so Sector 3 in your screenshot). Verizon uses this same format as well. I am working on adding this in a future update. Big improvements in the Reset feature coming too (sorry, you still need root on 4.2+ ). -Mike
  8. SignalCheck doesn't actually use any location features or GPS right now; the only "location" is the BSL identifying the base station you are connecting to. This is set by the wireless provider, and this question comes up all the time.. basically, Sprint uses an offset in many markets. See here: http://www.bluelinepc.com/signalcheck/help/#bslwrong The other possibility is that you are on 1X 800, and are actually connecting to a far away site because the signal travels much farther than you are used to. -Mike
  9. That is characteristic of free apps in general, and actually is above average. According to this study, 22% of apps are only used once -- and that doesn't necessarily mean it was uninstalled. That study also blends free and paid apps, and I would expect paid apps to have a much higher retention rate (as SignalCheck does). Also, apps like SignalCheck that have a separate paid version take a hit here; a lot of Pro users likely started by trying Lite, and uninstalled Lite after buying Pro. Even if only half of Pro users ever tried Lite, that's still at least a few percentage points. -Mike
  10. I had read about Google's Android build version scheme awhile back, and an article I came across confirmed the first thought I had when I saw your post. Here's the breakdown for those interested: K = Android version (KitKat) J = internal code branch identifier T = quarter of build (A was early 2009; T = Q3 2013) 49 = day of quarter (11/18/13 in this case) K = version of that day (A = first; so K = 11th version built that day) The key thing here is that the current public build is KOT49H, so it was built on the same day off a different code branch. Perhaps this new version is from a Google employee who was testing the other branch while it was being developed? It's certainly no guarantee, and I'm sure Google might reuse a date code for minor updates within a short time frame. But, it's been several weeks, and there doesn't appear to be a "quick" release on the horizon like there was for 4.4.1 (which also had a T49 version) to 4.4.2. Google has re-used the date code on minor updates in the past, but they were all from the same internal code branch, so only the last character was changing. But who knows.. this--along with all the other discussion about it--is pure speculation. Google is pretty good about keeping updates under wraps until they are ready to release them. -Mike
  11. Are either of you guys hitting the Reset Connection button (or menu option)? For some reason, the N5 is suddenly having issues with this lately.. but not every time, it's inconsistent. I've been seeing it myself and receiving reports from others. It will reset the connection, but the app freezes and must be force closed. Once you open it back up again, it works fine. The crash reports indicate it is not crashing at a specific point in the code, it's totally random -- which makes me think it's something external causing the issue. I have made improvements to the Reset code that will be included in the next update, but I don't think it helped the crashing. Wondering if there was a recent Google Play Services update that is causing this. That is the only thing I am aware of that updates itself in the background without any user knowledge. EDIT: Make sure you are on the latest version (4.22).. it fixes the issue where the background service was getting killed off. That caused the icons/widget to freeze no matter what your connection status was. -Mike
  12. LG isn't waiting for Google to stop releasing updates, they (and most other wireless providers) just spend a lot of time making their own specific tweaks to Android.. hiding features, custom skins, adding bloatware, etc. And lots of testing.. obviously no company wants to push out an update that lights up their customer support lines (or inboxes) because of a preventable problem. -Mike
  13. I'm just glad that I got the right idea at the right time, and decided to teach myself Java and how to create an app. I've enjoyed doing it and the compliments from S4GRU folks and elsewhere is very rewarding. If the compliments come from someone who knows what they are talking about, it's even more rewarding. It's starting to become bigger than I ever imagined, and I'm always trying to come up with new ideas to make it better. Unfortunately, a lot of the best ideas go up in smoke when I try implementing them! I saw a guy at the grocery store tonight wearing a "Verizon LTE Team" fleece, looked like he was probably an exec.. I really really wanted to interrupt his focus on selecting the perfect bunch of bananas, but I thought it might a little weird if a complete stranger started grilling a guy about his network in the produce aisle. Of course, if it was a Sprint fleece, I wouldn't have hesitated.. I don't mind sharing some numbers.. here are some stats as of yesterday. All totals are since 1/3/13, the first public release of SignalCheck Lite: Over 28,500 different users have installed Lite (86%) or Pro (14%) on at least one device at some point. Over 10,100 different users currently have Lite (73%) or Pro (27%) installed on over 12,700 devices. 30% of Lite users still have it installed. 70% of Pro users still have it installed. Users currently have Lite installed on an average of 1.16 devices, and Pro on an average of 1.52 devices. I am amazed when I think about how over 28,000 people tried one of them at least once, and it's still on almost 13,000 devices. Awesome stuff. My sincerest thanks to every single one of you! -Mike
  14. Thanks, I thought it was showing a different icon when you had Spark connection, that's what I was interested in. Never mind! -Mike
  15. Has anyone dug into the One Max and noticed if there are any Spark-specific APKs or other similar tidbits floating around? Very curious to know how Sprint is identifying Spark/non-Spark connections. Thanks, -Mike
  16. Well my sincerest thanks. In my search tonight I did notice that Brian has mentioned my app a few times.. the name didn't ring a bell, but when I did a little digging I was impressed and couldn't help but smile. Cool stuff.. still amazed and humbled when I think about how many people use it! -Mike
  17. I hadn't heard of it until recently, when someone else asked about it.. I started using it myself, and like it. I do intend to add a SignalCheck plug-in to it -- it's already on the to-do list. I haven't had a chance to look into it yet, but I will. Too many device/ROM-specific bugs are popping up lately, causing me to spend more time troubleshooting and less time adding new stuff. -Mike
  18. I don't do a lot with it, just try to announce app updates when I remember.. I also search mentions of the app once in awhile, and try to RT unsolicited positive comments about it that I happen to find. That's how I found your flattering tweet. Thanks, btw! @bluelinepc for those of you interested.. although if you already follow this thread, it's probably not all that useful. -Mike
  19. Like AJ said, you can't roam between Sprint and T-Mobile (on any phone). But, if you were asking if you had a Sprint account and a T-Mobile account, and wanted to swap between each with a T-Mobile SIM inserted and toggling between GSM and CDMA on the N5's Radio Info screen.. that doesn't work. I just tried it; with the T-Mobile SIM inserted, it will not allow any CDMA-only entries to be selected. You can use the N5 on multiple carriers by switching out the SIM, but a reboot is needed. It appears that you even have to reboot it if you remove and re-insert the same SIM; network connectivity is flaky at best, and usually goes away altogether until you reboot the phone. EDIT: Actually, CDMA 1X and EV-DO connections appear to work without a reboot if you have a SIM from a CDMA provider (like Sprint) inserted. However, no GSM, eHRPD, or LTE connections for any provider will work properly without a reboot. It appears that the phone initializes the 3GPP network stuff (like MCC-MNC) on boot, so once you pull the SIM, it won't properly initialize again until you reboot. GSM and LTE are both 3GPP standards, so that makes sense. -Mike
  20. The radio firmware/baseband will be different, but that is separate from the ROM. Unless other specs changed, it might be close enough to use the T radio with a 720 ROM. I'm sure someone on XDA will start playing around soon. -Mike
  21. Is there enough of a difference in the two devices where a 720 root method or ROM wouldn't work on a 720T? -Mike
  22. Yep.. and the closest site to my house has WiMax, should be one of the earlier Band 41 completions around here. Nothing yet, but B25 is so strong around here that it might prevent me from connecting to B41, at least until the N5 gets it's Spark update. -Mike
  23. Same here, I actually turned off 41 and 26 a couple of weeks ago to see if it made any difference on battery life. It didn't. I don't think we need to continue down the road of turning this into a G2 vs. N5 thread, they are both great phones that make my 6-year-old laptop look like an abacus.. -Mike
  24. Is it for appointments beyond March, indicating a possible daylight saving time issue? Are your time zones set correctly on both ends? I've been syncing calendars through Google for a long time and have seen some funky things on phones. All-day events appear to be a day off because of time zone issues, making an event from 11pm-11pm (or 1am-1am) instead of 12am-12am. -Mike
  25. If you were on stock, and know the bugs existed there, feel free to send it. I just don't want to blame Samsung for something that might be an issue with a custom ROM. If you're on a ROM that is just a tweak of the stock version, that should be fine too, it would share the same radio guts. That being said, I think the missing PCI exists across the board on their Sprint devices. If you're seeing the 31000 issue, that's probably happening on the stock ROM too. -Mike
×
×
  • Create New...