Jump to content

mikejeep

Honored Premier Sponsor
  • Posts

    3,271
  • Joined

  • Last visited

  • Days Won

    189

Everything posted by mikejeep

  1. I've mentioned it before; unfortunately Android does not provide a mechanism to get the band/frequency of any connection. Anywhere that the app is showing a band is doing so by evaluating available data (i.e. SID, PLMN, GCI, etc.) and determining if it matches a pattern that has already been identified as unique to a particular provider and band. I think it would be useful all providers, not just Sprint; I'm often asked by users on other networks to add this feature. Luckily, we have a heck of a userbase here, and enough data has been collected to identify some of the patterns that Sprint uses (CDMA 800, LTE B25/26/41). I don't have enough info on any other networks to add that information yet. But your idea of adding a separate "Band:" display (or "Band Class:", in the case of 1X) might be do-able, it just adds a little more clutter to the screen. I like a clean look, and make an effort to keep everything visible without scrolling.. that's easy on a Note or N5, but older devices don't have quite as much real estate -- and a lot of them are still out there. -Mike
  2. If you enable Preferences > Status Bar Icons > Hide Duplicate 1X icon, that should only show one status bar icon, even if you have the "Main" and "1X" icons enabled. Is that not happening? Or am I misunderstanding the issue? EDIT: Ahhh well what I just described _used_ to work.. I just played around with it on my N5, and apparently it done got broke somewhere along the way.. to the bug list it goes. -Mike
  3. Ha, apparently you beat me to my own punch! I must admit, I'm not in the loop with 1xAdvanced, and have not put a lot of effort into figuring it out. As far as the app goes, 1xA info has not been asked for, and I have plenty of other features keeping me busy at the moment so I have not pursued it. I see it mentioned around here from time to time, but nothing I happened to come across seemed to explain it in much detail. I do know that I am not aware of any way to determine if a connection is 1xA, as there is no such network type in the Android spec. -Mike
  4. I'm thinking along the lines of consistency; when connected to one of the "new" Sprint LTE bands, I am leaning toward having the LTE provider name showing "Sprint B26" or "Sprint B41" -- the "LTE" heading will not change. Perhaps I should consider changing that instead, but I like using the Provider name because then it can be easily seen in the notification pulldown or logs. Another consideration to keep in mind is that this is not a Sprint-only app, there are many users on other providers. And Sprint users do roam. So when Sprint User X bumps over to roaming on Verizon or elsewhere, it will then say '1xRTT' again. I feel that three possible labels just adds to the confusion. I don't think the use of 800 in the 1X provider name is going to have anyone infer that they are connected to LTE 800. A user who understands what a 800/1900/B26/B41 label is will not be confusing 1xRTT with LTE. One thing is fairly certain, the average SignalCheck user is a nerd I sincerely appreciate the feedback! -Mike
  5. I've been seeing a lot more confusion lately about [CDMA 800 | 1X 800 | 800 SMR | CDMA1X800SMR] as it becomes more widespread, and I think the way SignalCheck displays it might be fueling the fire. So I'm throwing this out to everyone for an opinion.. any opposition to changing the CDMA 1X label to always show "1xRTT", and changing the provider to display "Sprint 800" when appropriate instead? That would keep it consistent with how I intend to identify Sprint LTE bands, and (hopefully) cut back on the misinformation. Any/all opinions/ideas are welcome; if you're just going to "me too" something, just give the appropriate post a 'Like'. No need to clutter the thread with repetition. Thanks, -Mike
  6. That was my initial thought; the app is of limited use on a Kindle, even if it worked properly. I did look into it this afternoon, and there are some undesirable caveats with their Appstore: if you uninstall the Amazon app, anything you installed through it stops working; Amazon has the right to adjust your app's prices as it sees fit; and apps installed through Amazon will periodically attempt to connect to an Amazon server for license verification--if you do not have service, you lose access to the app until you're back in coverage. Not headaches I'm interested in dealing with. Well I am flattered that I had the honor of pulling that two bucks out of your tightly-clenched fists (I was no different -- I *never* bought apps until I started developing mine; if it wasn't free, I didn't think I needed it), but for the reasons I listed above, Mom will have to save those Amazon coins for something else. Thanks for the very kind words though!! EDIT: (Oops, I confused a couple of posters there.. but I'm leaving it, because there's nothing better than a Mom joke ) -Mike
  7. The site hint shows information that has no relevance to most people; it is the app's attempt to calculate a value that cross-references with some engineering information. "Sector F" is the app's best guess as to which CDMA 1X sector you are on. The way it is implemented in the current version of the app works in most Sprint markets; I have since learned of a few other methods (US Cellular, Verizon, and an alternate Sprint method) which will be options available in the next version. Usually the sectors are identified as 1/2/3, but not always. Your Sprint market might use the alternate method coming in the next update (I know that Boston does). Again, it doesn't have a ton of relevance to the average user -- myself included. -Mike
  8. I have never looked into it; nobody has ever asked for it, and while I shop on Amazon often, I've never even peeked at their app store. Is there a significant reason why someone would buy an app there instead of through Google Play? Seems like anyone interested in a nerdy app like this would be the Google type. -Mike
  9. I had similar problems for a couple of days, and it turned out that my voicemail-only Google Voice setup had somehow become a full GV integration, messing everything up. On the GV website it showed all my missed calls, but my N5 never made a peep. No idea how it happened, as I hadn't touched my GV settings for weeks. Once I figured it out and fixed the settings, everything was fine. I also discovered that SMS/MMS messages are not delivered to the N5 when in LTE-Only mode, even when connected to Wi-Fi. I accidentally left it that way for an entire day.. I have solid LTE at home, so I had no idea. I was bombarded with messages the instant I put it back into CDMA/LTE mode. Oops. There have been no CSFB issues in my market (Boston) that I am aware of, so that was not in play for my specific situations. That doesn't mean it isn't the reason others are experiencing problems though. -Mike
  10. 8000mhz?! I'm not sure which provder that would be useful on.. -Mike
  11. Hahaha!! I think it's the opposite, Amazon caught wind of my app and is trying to steal it. They will give up quickly when they realize mikejeep money is closer to Monopoly money than Bezos money.. -Mike
  12. You might see the roaming indicator, but it's a glitch.. you are not actually roaming. I have seen it myself. I think it might have something to do with the fallback from LTE to 1xRTT happening a split second before the incoming call hits. The N5 might not be "realizing" what network it is on yet, for lack of a better word. As I mentioned before, the CDMA routines in the base Android code aren't entirely perfect for single-path devices like the N5. It appears that there are telephony functions where a constant 1X connection was expected (which was a fairly safe assumption until last fall). -Mike
  13. Not sure? There isn't anything like that in this app.. is it an icon, or appearing somewhere in the pulldown? -Mike
  14. As was already mentioned, that data is limited to Sponsors only. I will tell you that your area does have the BSL locations offset, and there are at several Sprint sites within 10 blocks of you. So you would need to check the maps and then watch SignalCheck to try figuring out which site you were connecting to as you move around. In a dense area like NYC, it is trickier to pinpoint exactly which site you are connecting to until you can confirm which IDs belong to which sites. To do that, you basically need to play Marco Polo while you wander around watching your signal levels.. -Mike
  15. I haven't tested realtime Wi-Fi enough yet to say if there will even be any noticeable impact, but I do have some options like you mentioned in mind. When I first created the app, I had zero intention of including Wi-Fi info, and only added it because I was testing something different. I personally use Wifi Analyzer for my own needs (I highly recommend it), but I have learned how handy it is to have the basics in SignalCheck since I'm already running it. Looking further into the 802.11 specs, distinguishing a/b/g/n won't be bad, but yes, ac (and beyond) is a bit different and might not be feasible. Android doesn't report any protocol information, so the only way to get it is to figure it out based on speed and frequency. -Mike
  16. Not all post-upgrade sites squawk their actual locations.. in the Boston market, everything was offset pre-NV and post-NV. Some coordinates changed slightly, but are still offset. I do know that the 911 systems in this area have been reporting the actual site locations for several years, but who knows how much relevance that has to the 1X coordinates being broadcast. -Mike
  17. I'm not going to lie -- I was working on a bug related to LTE Only mode, and clearing up that happened to get EV-DO Only working too I could try adding the protocol in there; after looking at the 802.11 specs, it does look like the speeds reported by Android often (but not always) match the protocol-specific speeds (i.e. 65 Mbps indicates an 802.11n connection). I'm also evaluating the performance impact on realtime Wi-Fi data updates. Right now, it just updates the display whenever a mobile signal change is detected. If you go into Airplane Mode, you will notice that the Wi-Fi details never change if you leave the SignalCheck in the foreground. That one Google Play comment is the only backlash I have had about the persistent icon, but the option to stop the background service was something I was trying to get working for awhile anyway. -Mike
  18. I posted a message with details on the beta Group but I know someone else didn't get it either.. you should be able to see it on Google Groups. I should add an explanation for the site hint options.. 1 and 3 refer to the 1st or 3rd character position of the hex BID used to identify the sector; it varies by market. It should work fine but I will take a closer look at it this afternoon. In the meantime, try the other options, some are similar. -Mike
  19. 43 days until Opening Day! ;-) -Mike
  20. It is part of the baseband (radio software). Nothing you can do to change it other than flashing a different baseband version. -Mike
  21. mikejeep

    HTC EVO 4G LTE

    Ahh, interesting.. that's a completely different menu I've never seen on any EVO ROMs. But doesn't that menu have the same effect as setting the appropriate combinations of Domestic Data and International Data in the options near the bottom? -Mike
  22. Please don't post the same message all over the place.. I understand what you're doing, but keep the discussion in one spot. You're asking a network/CSFB/market question, not a device question. -Mike
  23. mikejeep

    HTC EVO 4G LTE

    I just signed on to post this myself, it's definitely there. Just installed the new update on my old EVO LTE.. very snappy, I'm impressed. Did not lose S-OFF or the custom PRL I had loaded on the previous version, although that might be because the phone is not activated at the moment. -Mike
  24. I like Mountek's (http://mountek.com) products; I have the nGroove and the nGroove Snap. Both are very similar, strong build quality. You can install it in a CD slot or dashboard crack. It holds VERY well and is easily removed, it snugs in with a thumb screw. The nGroove (apparently now called the nGroove Grip) uses an adjustable holder that works very well. The Snap requires that you stick a small magnet on the back of your phone. It's very thin (maybe a little thicker than a credit card?); I have mine slid in between my EVO LTE's Seidio Surface case and the phone, not adhered to anything. The magnets are strong enough that the case does not impede it, although I'm sure it does make the grip a little weaker. You could put the magnet on the back of the case if you preferred. For a more permanent solution, I have a ProClip (http://proclipusa.com) installed in my Jeep. You choose a vehicle-specific mount, then add on whatever device mount you want. I chose an adjustable version so I can use any phone, case or not. Mine snaps onto a lip on the dash, and included a small adhesive pad to hold it in place. I tried it without an adhesive pad and it held firm, but that probably depends on the vehicle. EDIT: No wireless charging with either option (don't think I've seen that in a car mount yet), but the charging port is accessible with both solutions. -Mike
×
×
  • Create New...