Trip

Mike, In the change log, you mention this: Added feature to add current location to a site note. I just now found it, having thought it meant something else. But my first attempt at using it, sitting here in my office at work, said "Location unavailable!" even though I have GPS coordinates shown at the top of my screen. (The GPS is not currently locked, however, since I'm indoors.) Not sure there's a bug here, but wanted to point it out. - Trip

Hard to press and hold a full-screen message that I need to update. (Which then defeats the "keep screen on" in SCP...) I'll check out fotakill. - Trip

Considering these phones are literally only used for SCP/NSG, I've rarely encountered such issues. My bigger problem, actually, is the constant prompting for updates that I can't install because I've replaced the bootloader. I can kill them, but on reboot, the prompts start right back up again. - Trip

Yep, that's it. I wasn't reporting anything in particular, just wanted to be sure you had at least one outside test of the saved submission functionality. And I don't reboot my devices unless it's necessary. The last time I rebooted that phone was probably in May when I turned it off for the flight back from Denver. - Trip

Sent it in. Let me know if it worked. - Trip

Very cool! I'll take my Verizon phone out with me tomorrow and try to do a diagnostic while I'm out and about. Then, when I get home, I'll try to submit it via Wi-Fi. - Trip

I did link to the City of Alexandria building permit site. - Trip

Wasn't sure where to post this. This thread seems as good as any. Went out and about last night and spotted this: http://imgur.com/Y1FdQb4 Do you see it? If not, here's a zoomed picture. http://imgur.com/vqbms0A That's a Verizon small cell. I knew it was there because of the -50 dBm AWS signal on my Verizon phone, but it took me a while to find it. When I got home, I found the building permit for it; it was apparently filed 12/15/16, issued 3/1/17, and passed inspection on 6/5/17. ( https://apps.alexandriava.gov/permittracker/CaseDetails.aspx?casenum=BLD2016-02856 ) I wish Sprint could move so fast... - Trip

Verizon and AT&T compete directly with the local cable company in many cases. In my area, I have Verizon FiOS, and Cox is also available (but significantly more expensive for whatever reason). - Trip

Three of my phone have SIMs and connect to the network, but have no service associated (two T-Mo, one Verizon). So it's definitely something I've encountered. - Trip

For a future build, it would be worth making it possible to dump the disgnostics into a file for later submission. I have several phones with no service that I am basically unable to send diagnostics as a result. By the time I'm home on Wifi on those devices, it's too late and I've lost whatever I wanted to show you. - Trip

I haven't updated this thread in quite a while. Here's what I'm using now. All rooted devices have Network Signal Guru for band locking and, with the exception of the AT&T phone which is now on Android 7 and uses the API method, for EARFCN retrieval in SignalCheck Pro. Verizon - I have a rooted Moto G4 Play, which is expecting an update to Android 7 any day now. Every 90 days, I swap out the SIM, and though it has no service, it does connect to LTE and provide information on the network. AT&T - I have a rooted HTC One M9, which is running Android 7. I recently replaced H2O Wireless with the new FreedomPop LTE-only SIM, which has a free 200MB monthly. The LTE seems more reliable on FreedomPop too. I replaced my Nexus 5 with the M9 since my sister on Project Fi needed a loaner phone when her 5X started to boot loop and I wanted a replacement phone with Band 30. (I've now gotten the Nexus 5 back, but it doesn't support the root method of EARFCN retrieval, it won't get an Android 7 update, and I don't know what to do with it.) US Cellular - I have a rooted Moto G4 Play, which is expecting an update to Android 7 any day now. I can put 30 days of service on it for $10, and it won't connect to LTE without service (US Cellular appears to be SRLTE only, so without service, it only connects to 1X). T-Mobile - I have a rooted Moto G3, which will not be updated to Android 7 from what I understand. The T-Mobile SIM has no service on it, but connects to LTE anyway. The phone does not support Band 12. T-Mobile - I have a non-rooted BLU R1 HD, which will not be updated to Android 7 from what I understand. It has a MetroPCS SIM in it, but connects to LTE anyway. It has a utility on it which allows band locking, but no ability to get EARFCN, so the phone is perpetually locked on Band 12 only. No need for EARFCN when you always know what it's going to be! I suspect there are now cheaper phones that would work, but I'm happy with what I have for the moment--for the most part. I'm keeping an eye open for something that's Band 66 capable with the idea of using it to replace either my Verizon or US Cellular phone (and using the G4 Play it replaces with T-Mobile and using the G3 for something else), but I haven't seen anything inexpensive in that category yet. - Trip

I suspect you're right. AT&T PCS in this area has an EARFCN of 850, not 950. I starred it as well. That's... really unhelpful if true. - Trip

That would explain the output of NSG, but not what's going on in SCP. Interesting. What does SCP show? And, of course, send a diagnostic to Mike, if you haven't already. - Trip

Those two pictures appear to be different cells. What's really weird is that the EARFCN being shown in the picture on the right is PCS, but the GCI sector ID matches AWS. And in the picture on the left, the frequency shown is within the AWS-1 band. - Trip

I don't understand why that means the PSC isn't logged for the connected cell though. Seems like useful information. And I actually have the PLMN matching turned off on the LTE side anyway. - Trip

Mike, Two things. 1) In the other thread, you mentioned neighbor cells for the GSM-based technologies. I want to point out that those appear to use PSC, a value that is not currently logged, to identify the neighbor cells. Since the value is not logged, there are never any labels attached to neighbor cells in that mode. 2) With respect to this, you may want to look into ImageMagick. It's open-souce software that can be used to write images from a command line. Theoretically, you could script the creation of images, thus automating the process for yourself. I'm afraid I don't use it enough to be a resource on how to use it. - Trip

Done. Could you just point all unknown bands to the generic "LTE" icons that used to be used for that sort of thing? It's a band-aid, I know, but it would save you some work right now. - Trip

My LG G5 does the same thing. I think it started with the upgrade to Android 7; I recall older versions showing me other bands, which was easy to spot on my Sprint phone because the B41 PCI is different from the B25/B26 PCI on a given sector. - Trip

I actually thought it was intentional, for devices that didn't report PCI. But I'd prefer it show 0 PCIs since most current devices do report the PCI. - Trip

Any more than "CTIA - The Wireless Association" or "NTCA - The Rural Broadband Association"? - Trip

My guess? S4GRU. - Trip

Mike, I'm currently connected to 00DFE217 (weird that it's following the Nokia pattern; it's a new site I've yet to track down), with a TAC of 20234. The GSM data has 20234 as the LAC and the CID is 57879, which is 0xE217, matching the last four digits of the LTE GCI. The LTE ASU is always 99 on this phone, but on GSM it changes, so I'm not sure if the ASU is being reported correctly for the GSM entry and not for LTE. I'm suspicious of some of the other numbers as well. My big problem is that it logs this faulty data to the GSM log, which then requires periodic cleaning. I agree that it will hopefully become a moot point, I'd just prefer not to have to replace my devices any sooner than necessary. Despite the promise of Android 7 when I bought it, it no longer looks like the R1 HD will get it, but it's otherwise still a very useful device because I can lock it to a band without root. (It has a MediaTek chip so I can't use the root method to get EARFCN anyway.) It's the only device I have that can't get the EARFCN at all; my G4 Play phones have the root method now and should have Android 7 soon, and my G3 has the root method. - Trip

Mike, I attempted to send diagnostics from my BLU R1 HD this morning; hopefully you got them. For as long as I've had it, it's listed both GSM and LTE at the same time. With a little bit of math, it quickly becomes obvious that the LTE data is being duplicated as GSM data for some reason. I assume the API is providing bad data, but is there any way to work around this issue, even if it means having a software setting for it somewhere? Additionally, I always lock this phone to Band 12, but with the new version, it now only reports "LTE" and never "LTE 700". How would you feel about adding a means of telling SCP that the phone only connects to a single band so all logs can be identified as that band (if EARFCN is unavailable)? - Trip

Are any other users here running rooted devices? Your report makes me wonder if our crashes are related--the app attempting to use the root method to read the neighbor EARFCN or something before permission is granted, or something along those lines. - Trip