Jump to content

mikejeep

Honored Premier Sponsor
  • Posts

    3,264
  • Joined

  • Last visited

  • Days Won

    186

Everything posted by mikejeep

  1. (Moved from elsewhere) Hmm.. wait, do you see 31000 or 310000? And do you EVER see 310120 (or anything else) while connected to LTE? -Mike
  2. It's not really the residents.. it's mostly the college kids from out of town who have mommy & daddy paying $60k for them to go to [insert any downtown college name here] who cause most of the trouble. Fenway is within walking distance of a ridiculous number of schools. But apparently Boston PD had fewer arrests than a typical Wednesday night.. an overwhelming majority do "get it", marathon bombing or not. One car flipped over, 9 celebration-related arrests throughout the night, no injuries. The Bruins beat Vancouver in 2011, and there were 2 arrests in Boston that night, while Vancouver suffered $5 million in property damage, 100+ injured, 100+ arrested. It's all stupid. Anyways, to stay on topic: has anyone else seen "Sprint B41" appear in the app? Please post if you do, I'm curious about this.. And an app re-design is about half done. Was hoping to have it out right after the first tri-band devices hit the air, but that date is coming up a little faster than I can work. Blame the Red Sox -Mike
  3. This is most likely an intentional feature of Android. When you shut your screen off, Android tries to put as many background processes to sleep that it can, in order to conserve power. There are methods to prevent this from working (Sensorly is a great example of this--anyone who has tried to turn off their screen while mapping knows what I mean), but I do not implement them. Once you turn the screen back on, everything "wakes up", which could explain what you experienced. The way SignalCheck runs prevents Android from putting it to sleep 100% of the time, but it does in some instances, based on lots of factors that your system monitors. The "Keep Screen On" feature exists for people who want to have the real-time signal information; as long as the screen is on, Android will not force anything to sleep. As long as SignalCheck is in the foreground, it will not be killed off for memory reasons. Once an app is put in the background, the system decides what stays and what goes. I don't mess with this on purpose -- I feel that Android does a very good job with resource management. If your device thinks there is something more important that needs CPU or memory that SignalCheck is using, I feel that it should have the right to de-prioritize SignalCheck. -Mike
  4. Yeah, a lot of engineering screens have it.. unfortunately I don't have the same double-secret access to the radio data that the engineering screens do! I have had my eyes open for a cheap Optimus G to use as a testing device to see what I can dig out of LG phones. I hate the manufacturer-specific stuff, it complicates coding and testing tremendously. I have spent dozens of hours messing with Samsung code. Hopefully as more devices with Android 4.2+ preloaded hit the market, they will take advantage of the new features built into the Android API that SignalCheck takes advantage of. It's only for LTE info, but that's quickly becoming the most important anyway. -Mike
  5. Celebrating, HELL YES!! Not flipping any cars though.. I'm too old for that these days, plus that was never my style. Doesn't make any sense to flip cars over and light couches on fire when you win (or lose). Can't wait until Saturday, when I go to Boston's eighth championship celebration in the past 11 years.. -Mike
  6. I did something similar almost 10 years ago myself! Comcast kept telling me there was nothing wrong with the signal to my condo, despite the fact that suddenly started losing certain TV channels and internet at consistent times of the day. Wrote a quick signal logging script and ran it for about a week. Sent them the logfile showing the cable modem signal strengths sharply dropping at the same time every day, and that did the trick very quickly. No idea what the issue was, but I lived there for a couple more years and never had issues again. Maybe I had a neighbor with a jacked CB setup.. -Mike
  7. Hmm.. either Sprint has your device set up to default to 311490, or they are broadcasting Band 25 LTE on it in your area. Strange that the engineering screen shows the "regular" 310120 but the app sees otherwise. PM me your e-mail address, I have something for you to try. -Mike
  8. The Pro version can do it.. go into Preferences > General Settings > Enable Orientation Sensor. Piece of cake EDIT: Seriously, I got out-posted by 30 seconds? In the middle of the night? Haha... -Mike
  9. The latest version of SignalCheck (4.17) should address both of these issues. The carrier names in the pulldown are now properly shown for each individual connection, and the 31000 bug was addressed. -Mike
  10. It could be that your device is killing off the piece of SignalCheck that listens for signal strength changes.. that routine would be what updates the icon. By going back into the app, you're restarting that listener. Android handles memory management itself, and if it needs resources, it might see SignalCheck as a process that had been running in the background for a long time with no foreground activity, which makes it a reasonable candidate to be killed if necessary. -Mike
  11. I was about to congratulate you for being the first person to report being on LTE Band 41, because that is what B41 is supposed to indicate in the app... but then I saw you are on a S3, so that's impossible. That's a new feature rolled out in the update this week.. clearly one that isn't working right. Can you post a screenshot next time you see it? Any chance you noticed what MCC/MNC (the number in parenthesis next to the LTE carrier name) you saw at that time? 310120 is the normal Sprint LTE one, and really the only number you should see right now on an S3. Perhaps you hit a site that was broadcasting what we thought might be one of the Band 41 MCC/MNCs on Band 25. Or I messed up the app, which is more likely.. -Mike
  12. Just taking a guess here.. looks like your SignalCheck icon shows dashes, are you having an issue with EV-DO info not showing up in the app? Or does that post you took a screenshot of mean something? Or is this in the wrong thread? -Mike
  13. That is odd.. the "High" priority setting uses nearly the same priority as the previous (non-configurable) versions did.. PM me your e-mail address and I will send you a small update to try. This is the first report I have had of this behavior. Anyone else out there seeing this issue? -Mike
  14. I think I get what you mean, but I'm still confused because I thought Sprint officially launched the market and city of Boston in January.. https://community.sprint.com/baw/community/buzzaboutwireless/network-and-coverage/blog/2013/01/28/sprint-brings-4g-lte-to-boston-austin-and-growing-number-of-cities-in-2013 Not that it matters, I know the announcement itself is just a marketing/PR thing, the network itself has been chugging along for months.. just curious. -Mike
  15. SignalCheck displays the base station ID exactly how the phone reports it -- no editing on my end. Perhaps if you do some kind of decimal/hex conversions on the number you see on the debug screen, it corresponds to what is showing in apps? This is the first I've heard of anything like this. There are no other data points that I am aware of that would represent a sector with a single digit. -Mike
  16. Haha!! Sometimes I outsmart myself. Glad to hear it works.. this update was a result of 6 weeks of code changes, a lot of which were behind-the-scenes-cleanup that probably fixed several small issues similar to yours. The "Site Hint" does some math on the BID and displays the result in a format that matches engineering information that a few people have. There was a discussion about it earlier in this thread. If you don't know what it is, you're probably not one of those people.. so you don't need it. -Mike
  17. How does that mean it's wrong? It just indicates that the route between your device and whatever speed test server Sensorly is using has higher latency than whatever server you've used before.. -Mike
  18. Looks good guys, nice job! FYI, Sprint site locations in some markets is off by much more than 100-200m.. sometimes it is miles. Many sites near me are offset by about 1.5 miles, but it varies quite a bit. Keep up the good work. -Mike
  19. The app will show the carrier name and site IDs on 1X and LTE connections; only HTC devices can show the EV-DO/eHRPD carrier name and sector ID. You are correct, Android does not have a standard method to get the EV-DO information. Thank you, I couldn't remember who brought up the GSM issue! Are you able to confirm that the values are correct, or just that they are about the right length? I found 3 different explanations as to what the "long CID" is, so I'm not sure if I implemented the correct solution or not. -Mike
  20. Expanding on what AJ said.. if you're referring to the icon, "3G" is shown when there is a valid 1X, EV-DO, or eHRPD data connection, and "4G" icon is shown when there is an LTE connection. No icon is shown when there is no data connection available. If you're referring to the signal bars, HTC devices show the 1X signal strength no matter what you are connected to. EDIT: Apparently the signal bars will show your appropriate connection signal strength if you have newer firmware. Older devices/software always show your 1X signal strength. All of that assumes you are running stock software. There are modifications and ROMs that can customize all of that. -Mike
  21. mikejeep

    HTC EVO 4G LTE

    Battery drain is far less of an issue than it was with WiMax devices.. basically a non-issue. Sure, every process uses at least some power, however I have not seen any evidence that shows that enabling/disabling LTE or changing the polling rate has a measurable impact. -Mike
  22. SignalCheck Pro has FINALLY been updated! Version 4.17 is the latest incarnation, and will be available on Google Play within the hour! This update is well overdue, thanks for your patience.. and thanks to my beta testers for their help. There are many changes, here is a summary, roughly sorted by importance: Added limited recognition of Sprint LTE Band 41 connections. Until tri-band devices are officially launched, this is largely untested. Early adopters should see "Sprint B41" as the carrier name if connected to LTE 2500/2600. Further expansion of this feature is planned, with alerts/icons/etc. Changed Preferences menu; options now organized into groups on separate pages. (Pro) The preferences screen had grown too large, so features are now categorized into sub-menus. Everything is still there, just organized better. Added optional alert for when LTE connection is lost. (Pro) When enabled, these alerts will trigger when an LTE connection is dropped. Added optional alert for when Sprint 1X 800 MHz connection is lost. (Pro) When enabled, these alerts will trigger when a Sprint 1xRTT 800 MHz connection is dropped. Changed notification pulldown to display data connection carrier name instead of 1X carrier name, if available. (Pro) This should clear up confusion while roaming; the main status icon (EV-DO, eHRPD, LTE) pulldown will now display the connected carrier name of that connection. For example, if on Verizon 1X but Sprint LTE, the notifications in the pulldown will now show Verizon on the 1X connection, and Sprint on the LTE connection. Previous version would have shown Verizon on both. Added option to hide main status bar icon when 1X status bar icon is enabled and active connection is 1X. (Pro) Basically, instead of seeing two 1X icons, you will only see one. Added option to set priority of status bar icons/notifications. (Pro) Icons can now be set low, medium, or high-priority in order to change their position on the status bar and notification pulldown. Corrected GSM CID field to display integer instead of hex value. Someone pointed this bug out to me, but I can't remember who.. thanks, whoever you are kalev76! Added optional secondary GSM status bar icon to display GSM signal strength when connected to LTE. (Pro) GSM users can now have two icons if connected to LTE, to monitor both connections. Added option to display “site hint” which may assist some users in determining the ID of the connected 1X site. (Pro) A few Sprint users will find this useful, but most will not. If you don't know what this is, you don't need it. Resolved issue with invalid LTE SNR information; LTE SNR will now be hidden if invalid. Some devices do not report LTE SNR and showed garbage data instead. Added dBm-only option for CDMA 1X status bar icon. (Pro) Resolved issue with dBm-only status bar icons disappearing when there is no signal. (Pro) Resolved issue with invalid/missing signal information on some newer devices. Resolved issue with “Unknown” carrier display and LTE MCC/MNC 31000. The free version, SignalCheck Lite, will be published in about a week. Upgrade to Pro if you can't wait, earlier updates is one of the perks! -Mike
  23. Weird. Aha, Gingerbread.. probably not frozen, but delicious none the less! There isn't much I can do, as your device simply isn't behaving the way it's supposed to. I am always tinkering with the code, maybe I will accidentally fix it in a future release without realizing it! Speaking of future releases... -Mike
  24. Very strange! Thanks for trying, I really thought that would do the trick. Engineering screens often pull data directly from the radio, they don't usually use standard Android routines. What Android version are you running? I know it's an older device, but I don't understand why it works and then stops updating.. and that bugs me -Mike
×
×
  • Create New...