Jump to content

mikejeep

Honored Premier Sponsor
  • Posts

    3,256
  • Joined

  • Last visited

  • Days Won

    183

Everything posted by mikejeep

  1. You're crazy. Lite has never had preferences, just an annoying box that pesters you to upgrade when you click the option. The code is not even in the APK. -Mike
  2. No problem, glad to do it! Always flattered to hear when non-S4GRU folks in the industry actually think I did something useful. Hmm.. PER.. maybe PN? Or BER? IBC maybe? The PN is something I've been trying to dig out for months, it's available on the engineering screens but I haven't been able to find a way to pull it into the app. I can think of a few people on here who would [attempt to] do cartwheels if I got that in the app. BER is the bit error rate percentage on GSM devices; it's already in my app, but you won't see it if you're on a CDMA provider like Sprint. Only GSM users, like AT&T/T-Mobile/international people would see it. -Mike
  3. You can leave the first two items unchecked and it will upload your data as you go. If you check either of them, it still collects the same data, but limits when it actually uploads it to Sensorly's servers. My interpretation of the 'wake to report to server' option is that it will wake up your device to send pending data if you had no Internet connection but it has reconnected. -Mike
  4. Ugh! Some devices just like to buck the system. I haven't had any reports of this on an Epic (or any other device actually). It must be the way the RIL shows the data. PM me your email address and I will send you a troubleshooting APK, maybe I can figure it out. -Mike
  5. Yes, that is something I've been working on; maybe I can get it wrapped up for the update I hope to get out next week. Right now it only re-queries the geocoding server when the reported lat/long changes, but that's still a lot of queries. Yes, the latest version (4.06) does. Even if you are on a custom PRL that changes your home provider, it should show the actual network you are connected to. -Mike
  6. Are you sure it didn't say Exception instead of Restricted? That's a bug, it is fixed in the next version. I accidentally left some testing code in there. You may or may not have been on LTE.. if you were, it was probably only connected to that site for a brief moment. -Mike
  7. Impressive! I saw something similar last summer before we had 800 around here.. I was hitting a 1X site in Maine from near the end of Cape Cod. It was not very usable for data though, it was much weaker than what you saw. -Mike
  8. SignalCheck Lite (it's free!) was just updated to version 4.06L on Google Play. I'm also suddenly receiving lots of reports of stale LTE data being displayed on more devices than just the HTC One. Nothing changed in the code, but I am guessing that the number of people in LTE areas has grown so much that pre-existing issues are just coming to light now. More LTE coverage is a good problem to have. The next version will alleviate all of those issues; it will only show LTE data if the current data connection is LTE. I plan to add an option for users who would prefer the old way, to still "see" LTE signals your device is not connecting to. I'm making decent progress on brand new logging/mapping features.. still needs work though. -Mike
  9. There are hundreds of entries listing law firms in all of the SID lists I was able to find. I almost deleted them all (the app will show the numeric SID if there is no matching entry), but decided against it in the end. Perhaps I will move forward with that idea.. makes more sense to show a SID than a bunch of names that will only end up confusing people. lordsutch, I'm going to send you a PM.. -Mike
  10. I contacted Best Buy today and got an immediate response telling me the codes are taking about a week to get sent, but I will be getting one. That's cool. Streaming through the YouTube app on my phone and website on my laptop seem to work well for me. I think all of it will improve over time; clearly the public has an interest in a device like this so I have no doubt that Google will put a lot of effort into it. -Mike
  11. Ordered online, did in-store pickup.. didn't get a regular register receipt, just the full-sized piece of paper saying what I had picked up. Nothing was on any of the online order confirmation e-mails either. -Mike
  12. The only apps with support are YouTube, Netflix, and Google Play movies/TV/music. I assume many more apps will include this soon because of the crazy popularity at launch. Chrome tab mirroring is better than I expected (see my last post), and solves issues if you want almost anything on the Internet to be on your TV, including streaming video from other sites. You can use file:// URI's to play local files I believe as well. -Mike
  13. I picked one up from Best Buy the other day as well, it was hard to find but I grabbed one. Haven't gotten my Netflix code they promised, but I know Google ran out of them so I might be out of luck on that one. Didn't stumble across this thread until today. If you're aware of the device's capabilities, it's a steal for $35. The dongle is small, and like others said, if you have HDMI 1.4 you don't even need USB power. I wasn't aware of the power issue and was a bit annoyed at first, but in the end it was no big deal. The device is very easy to set up, you just need a computer handy and your wi-fi password. Casting from Chrome works better than I thought; on my newer Vizio LCD, I watch live streaming baseball games through MLB.tv with it and it looks like regular HDTV, no issues whatsoever. On my older Panasonic plasma, the video is HD-quality but a little choppy. Once you watch for a minute or two you don't even notice it. Hopefully MLB.tv comes out with direct ChromeCast support soon and that issue is resolved. Overall, the casting feature seems to work excellent. If you're not doing streaming HD video, picture quality is excellent. There is about a short delay from the time you do something on your PC to when it shows on the screen, probably about 1 second on average. One interesting thing is that there is no security on the device itself. I don't think there is anything stopping my neighbor (whose wi-fi network is in range) from adding my ChromeCast to his wi-fi network and streaming whatever he chooses to my house. During setup, it searches for all ChromeCasts in range. It could make for some fun pranks, especially in dense areas. -Mike
  14. Heh, that would be a problem.. you're definitely not roaming on AT&T. What SID were you showing? That's what it is based on. -Mike
  15. I see what you are saying, but like digiblur said, a wide variety factors will affect your signal levels, not just distance from the site. Keep a chocolate bar in your pocket, and when it suddenly starts melting, you're close to the antenna.. when your phone suddenly starts melting, you're too close to the antenna. -Mike
  16. Excellent, glad to hear the CID's are displaying properly. Location features are in progress; I was leaning more towards logging than displaying the lat/long on screen, but I can consider that too. Video overlays?! You guys are killing me.. we clearly need to find better ways to waste our time.. -Mike
  17. I don't think your a phony, the speedtest app was probably getting a great connection and just over-reported the numbers. Try different speedtest servers and see how the tests compare. You probably did have a great LTE connection, but the true speeds were closer to 20-30 mb. -Mike
  18. Go ahead and post it here so if there any doubts it can be discussed. I don't need a screenshot, just the SID, what network you're seeing, and what network you think it should be and why. Like digiblur and a couple others have mentioned, there are some things in progress on the CM nightlies right now that are causing weird values.. -Mike
  19. Well at least after some Googling I was able to figure out what the heck you were talking about.. Is that accurate, or an old entry that should be Verizon now? I'm not going to fix it just for you, but I am curious. -Mike
  20. How long did it stay like that? I doubt it had anything to do with the app, I don't mess with the SID/NID/BID, just display the raw values the phone is reporting. Are you on a CM nightly? They have been tweaking the code to improve LTE data reporting on HTC devices; I know there was a recent bug where they had messed up the SID/NID/BID. Perhaps they are working on similar features for other devices (fingers crossed). If you see it again, check your 1X engineering screen and see what it looks like. EDIT: Nevermind, lordsutch is up at this crazy hour too, and he posted a better answer while I was typing! Hah.. -Mike
  21. Good thing... the FCC might start knocking on your door if you're using those kind of frequencies.. In all seriousness, you actually just gave me a bug to fix. I know exactly what is causing it, I bet AJ already figured it out too! You might see it once in awhile, but it's an invalid reading. I'm guessing you will most likely see it immediately upon connecting to LTE or right as you lose the connection. I stumbled across another post where someone else had similar readings with a Samsung device a year ago. -Mike
  22. AJ, I thought you might chime in when you saw that feature! I discovered how to pull the DL channel, and was trying to figure out how useful it might be. Then a little birdie (coughdigiblurcough) reminded me of your article showing how to do the calculations, I learned what an EARFCN was, and I was off to the races. I'm laying out the groundwork for some sort of basic logging component with a possible cloud implementation, but its still in the very very very early stages right now. I have some ideas that might dovetail into your thought about keeping an eye open for new LTE channel activity. -Mike
  23. A SignalCheck update has [finally] been released! Version 4.06 should be available from Google Play within the hour for Pro users. Lite users will receive their update in a few days. Here are the changes: Added LTE connection frequencies on HTC devices. Not sure how useful the exact freqs are, but the uplink and downlink center frequencies will be displayed. Feedback would be appreciated.. I found a way to get the info, so I figured I would share it. Added menu shortcut to hidden system menu on Samsung devices. (Pro) A step in the right direction for the Samsung folks! Figured out how to get something working at last.. this will bring up a menu with many system functions, including engineering mode. Still trying to get more functionality for Samsung devices, but it's painstakingly slow. Added option for users to set the Reset Data Connection delay time. (Pro) The default period of time the radio goes offline has been increased to 4 seconds, but now users can set it however they like (0-15 seconds) in the Preferences screen. Improved BSL feature; map link is active even if the address cannot be displayed. (Pro) The map uses the latitude/longitude, not the street address, so it should work just fine. The street address will likely display in your mapping app once it loads. Changed the "failing" message, since the site was being located, the app just can't connect to the geocoding server to determine the address. Improved display of CDMA mobile carrier names; will now show carrier names at all times, including while roaming or otherwise connected to another mobile network. The carrier name will now reflect whatever 1X network you are connected to; even if you are roaming or using a custom PRL that "fakes out" your phone, it should accurately show what carrier you are connected to. No more memorizing SIDs or needing another app to check who you are roaming on. Improved Reset Data Connection feature; only the cellular radios will now be reset. (Pro) Only the cellular radios should reset now when you use the RDC function. There is a known bug in Android that might cause your Bluetooth to continue to reset. If so, restart your device and it should be ok. You must activate the RDC feature at least once before rebooting for this to work. Resolved issue with Google Maps 7+ displaying an error when mapping the BSL. (Pro) The new version of Google Maps broke a lot of stuff, but I got it working again. The BID will no longer display on the map, but I hope to implement maps in the app itself soon anyway. Resolved issue with stale LTE data displayed on the HTC One after LTE connection is lost. I am working on fixing the underlying issue with HTC's engineers, but in the meantime, a temporary fix is in place for One users. No more bogus LTE readings frozen on the screen! Resolved issue with widget always displaying GSM connection type as “N/A”. (Pro) The widget was not displaying GSM connection types.. it will now. Updated EV-DO labels to display eHRPD if connected to eHRPD or LTE. Just trying to keep everything consistent, accurate, and simple. Updated help screen to reference the online FAQ page. This hopefully makes my life easier. If you have questions, please look there first. Updated LTE CID field to display in hex format. CyanogenMod 10.1 users running the latest nightly on some HTC devices are now seeing the CID field implemented in Android 4.2. Please let me know if this is not displaying properly after the update. As always, please let me know if you discover any bugs, and a huge thank you to my beta testers, especially mrrogers1 who put a lot of time into this release conducting tests and providing feedback! -Mike
  24. Listen, if you yahoos are going to resort to climbing towers to create "bugs" for me to fix, I'm going to give up!! Yes, digiblur is correct, each signal level icon is not text, but a graphic that had to be created individually. I created icons to cover -139 through -40. I will come up with something creative in a future release for readings better than that.. -Mike
×
×
  • Create New...