ingenium

Then how come when i cycle airplane mode during this event LTE shows and identifies as it should, with no 1x displayed? The only reason I think it is doing this is because it does not get the GCI. That is the only thing missing under signal check during this.

Mine almost always still displays 1x after airplane mode. Or if it doesn't it appears again very quickly. Missing the GCI and PCI is the main reason why the LTE data is incomplete and is what makes it frustrating. There must be some other method to obtain it though, since other apps can get it successfully, just not SCP.

 

AJ, that definitely makes sense that the phones have started keeping track of both.

 

Sent from my Nexus 6

I'm not confusing it with iOS, I've never owned an iOS device. But I have watched them both update in LTE Discovery. I don't know how it happens, but it does. SCP is also unable to show GCI and PCI information when it happens, while LTE Discovery does (I've watched it change bands as well).

 

Perhaps the phone "thinks" about switching to 3G for whatever reason (signal quality, congestion, something else?) and is periodically checking 1x quickly before switching back? I don't know.

 

Sent from my Nexus 6

 

Case in point, here are 2 screenshots I took seconds apart. Signal levels for both change.

 

Sent from my Nexus 6

You're intermixing how IOS devices and Android devices handle things. Signalcheck cannot show both at the same time properly because it's not possible. The sole reason 1X data is showing while LTE data is showing currently is due to a change in Android 5.0+ that is causing it to report false information or causing stale information to hang around.

I'm not confusing it with iOS, I've never owned an iOS device. But I have watched them both update in LTE Discovery. I don't know how it happens, but it does. SCP is also unable to show GCI and PCI information when it happens, while LTE Discovery does (I've watched it change bands as well).

 

Perhaps the phone "thinks" about switching to 3G for whatever reason (signal quality, congestion, something else?) and is periodically checking 1x quickly before switching back? I don't know.

 

Sent from my Nexus 6

The problem is, it is not supposed to work this way. A single radio device (which all tri-band phones are) should not be able to connect to 1x and LTE at the same time. One technology at a time.

It definitely shouldn't work this way, but signal levels for both update at the same time. My non-scientific observations seem to be that if it ever connected to 1x and switched to/from LTE, then when connected to that LTE site it also shows 1x data. Is it possible that it's quickly switching to 1x occasionally to check the status for eCSFB reasons?

 

I'm also fine with SCP displaying both sets of information. The problem is that basically all the LTE details are missing when this happens, but the details are there in LTE Discovery so it must be available somewhere.

 

Sent from my Nexus 6

So there's nothing that can be done to show more info with the 1x + LTE bug is present? As it is now, SCP has become useless on the Nexus 6. The bug is constantly present, so nothing get logged and the info screen has nothing useful. Airplane mode toggling fixes the issue maybe 25% of the time, and it comes back within 15 minutes. LTE discovery is able to still pull the GCI (and thus band) along with neighbor cells:

 

 

 

How even!!!??? B41 doesn't even go a mile here in Seattle!

The site is on top of a large hill, and most of the distance was across open water (SF Bay). There are a couple buildings between the bay and where I was at, but it's close to line of sight. I quit connecting to it once local B41 sites started coming online, but it still shows in my neighboring sites in SCP with a signal of around -115.

 

Sent from my Nexus 6

So I have a question that might stir up a little chatter here. 800 is known to obtain usially better distances than the 1+GHz. I'm curious about approximate maximum distances and locations of connections that others have attained made either with LTE or 1x800.

 

My personal best happened a couple days ago in the morning via 1x800. I connected to an 800 site just north of Pittsburgh, PA metro from approximately 30 miles east of Cleveland, OH. I crunched some numbers with the coordinates I had of the site (likely an offset, but probably not an enormous difference) and of my device and it came out to a little over 70 miles away. I was cheating a little. I learned years ago that morning propogation enhancement on VHF/UHF frequencies via tropospheric ducting often occurrs in my area. And it is often times even more enhanced in the spring and fall months.

I've actually gotten B41 (from a Clear site no less!) over a further distance than 1x800. I've connected to a site about 10 miles away on 1x800 (physically in Ohio, but the site was in Pennsylvania). On B41 I've connected to and used a site 13.2 miles away. 

B26 actually does seem to be optimized here in NW Chicagoland. My nearest tower is a mile and a half away and I still get at least 2 bars in my house. When they first turned it on it was pretty similar to B25 penetration, so I would bounce to 3G a lot.

 

I'll drop to 3G in my basement now but it's not a huge deal since I have pretty good wifi.

 

 

Sent from my iPhone using Tapatalk

B26 appears to be optimized in SF as well. Very few sites don't have B26 (basically every B25 site does). I think we'd be able to get away with VoLTE.

 

That said, I don't see the harm in enabling it, but letting it default to off. Don't advertise the feature yet. Let users discover it and turn it on in the settings. Sprint can use the data to fill in the coverage gaps and work out the bugs before an official, advertised rollout.

 

Sent from my Nexus 6

Slightly creepy

I live only a few miles from Patriot.

 

AJ,

What are your thoughts on the possibility of the engineering screens showing more info in the future?

Is this a Huawei or Google issue? (Not showing any info)

 

Sent from my Nexus 6P using Tapatalk

I'm also wondering what APIs the engineering screens use, and if it's possible to reverse engineer it and add new functionality.

 

Sent from my Nexus 6

Ha-ha. That's all there is. Sorry to disappoint.

 

Sent from my Nexus 6P using Tapatalk

Oh no! Does SCP at least work?

 

Sent from my Nexus 6

Hey guys, I just noticed something a little strange after the 6.0 update with the calculator app. In the top left corner it says "RAD." I can't figure out what it means and it doesn't seem to do anything.

 

Wondering if anyone knows anything about this or if it's just something that's just there now.

Radians. It can be toggled to degrees by swiping from the right side. It changes how trigonometric functions work.

 

Sent from my Nexus 6

Regarding the broken 1x/LTE on the Nexus 6 post Marshmallow, it seems LTE Discovery is able to consistently work. It shows the correct info even when the LTE engineering screen is missing the PLMN and Serving Cell (which triggers the bug in SCP). I tested it on known sites and it has the correct GCI.

 

So LTE Discovery must be reading the information differently than SCP or the engineering screen.

 

Sent from my Nexus 6

If you are relying on Signal Check Pro don't. Since upgrading to Marshmallow Google screwed up the LTE info that SCP uses. I was thinking that I was on band 25 alot until I checked the LTE engineering screen manually. For some reason Google's info is reporting that every band is band 25.

 

Sent from my Nexus 6 using Tapatalk

Hmm you're right. LTE Discovery displays the correct info, but Signal Check Pro and the LTE engineering screen do not. The engineering screen is missing information that LTE Discovery shows.

 

Sent from my Nexus 6

You'll love the new radio.

 

Sent from my Nexus 6 using Tapatalk

Other than it breaking the engineering screens (and thus SCP) if it drops to 3G at any point. Even airplane mode toggling doesn't reliably fix it. It seems you just have to wait it out usually, which can be a minute or 2 or a few hours.

 

Sent from my Nexus 6

Here you go (see attached)

Awesome, thanks for that. Got a new band 25 confirmation and band 41 confirmation (dual carrier too). I'll include it in the next map update. It's site FS16XC012 btw (corresponds to all the log entries except the very last one in your screenshot, which is a SF site we already had confirmed).

 

If you can send me your full text log I can go through it to see if you have any other new sites.

Dougherty Valley area in San Ramon (94582) getting B41 coverage now, so I guess they just turned it on. Have had B25 for the last 2 years or so, but just noticed B41 is active.

Do you have any Signal Check logs you could send me? I can add them to the B41 map.

 

Sent from my Nexus 6

Any idea how it works on Marshmallow with an older radio baseband?

 

-Mike

I haven't tried it personally, but I saw a report on XDA that older radios don't work or have problems on Marshmallow. I'm guessing they're using some feature in the newer radio that isn't present on older radios. Might be worth trying anyway though just to confirm.

 

I'd also be curious if the M radio has the same issue on Lollipop. For what it's worth I tested the M preview 1 radio for a bit on Lollipop and it didn't have the issue, but I read there were some noticeable changes in service between the M preview 3 radio and the final M radio so perhaps the issue was introduced there.

 

Any chance of being added to the SCP beta so I can test it on M?

 

Sent from my Nexus 6

Do you get the error on an active data session or is it only when your in an idle state? If the 1x disappears when a data session is started how long does it take for the 1x data to disappear from engineering screens.

With the new radio on the Nexus 6, an active data session does not fix it. Pretty much the only way is an airplane mode toggle, which works about 50% of the time (the other 50% it still has the bad data and I have to try again). When I first updated my phone it seemed to fix itself on it's own a couple times but since then I've never gotten it to correct itself without an airplane toggle, even waiting over an hour.

 

Sent from my Nexus 6

Late reply I know, but I decided to keep my airave. I get approx -100 dbm to -118 in my house from a clearwire conversion nearby but the 3G is still terrible. Either I can't pick it up or I get rssis north of -102 which won't send a text. Wifi calling is great, but I'm hoping for VoLTE and SMS over LTE soon so I don't have to rely on wifi so much. There are a few other areas that I go to a lot where there is -80 or so B41 but no CDMA singnal so I can use data but I can't place calls or text lol. Hopefully sprint will deploy IMSs soon and that problem will go away.

SMS already runs over LTE via IMS. Only phone calls drop back to CDMA. So you should be able to text fine on Clear B41

 

Sent from my Nexus 6

After the Android 6.0 update it causes SCP to often not update on the Nexus 6. On Android 5.1 everything worked perfectly. The engineering screens also seem to be affected, showing incomplete data. The phone reports being connected to LTE while these screenshots were taken (I turned wifi off to check after taking the screenshots):

 

 

 

 

I do not think this is as much an Android 6.0 issue as it is a 2015 Motorola issue. The above behavior also afflicts the 2015 Moto X, which is on Android 5.1.

 

AJ

Interesting. It was rock solid for me before upgrading to 6.0, so if that's the case perhaps it's the new 6.0 radio that inherited this "feature" from Motorola...

 

Sent from my Nexus 6

So it seems Android 6.0 is a huge step backwards when it comes to SCP and using engineering screens. Both often fail to update, show LTE when not connected, incomplete LTE data, or stale LTE data (wrong band, conflicting data, missing GCI or PLMN, etc). I've never seen the 1x and LTE "bug" in SCP until now. Even the engineering screen shows partial LTE data while on 1x. It seems to correct itself after 5-10 minutes, or toggling airplane mode. The biggest surprise to me was that the engineering screens are also affected.

 

I'm guessing it may have something to do with M trying to improve battery life, even though it also happens while charging. It's a shame, because it's going to make finding site updates with SCP logs much more difficult.

 

Sent from my Nexus 6

Here's a technical question I have, does Sprint's version of WiFi Calling work off IMS?

I don't believe so. My understanding is that it's basically mimicking an Airave (ie the same protocol over an ipsec tunnel). So my guess is the protocol predates IMS.

 

That being said, I don't see why they couldn't implement IMS based wifi calling along side it. It would be a good proving ground before moving to VoLTE, since I believe the backend is the same.

I've been mashing check update and nothing yet.

It's a staged rollout, so hitting it more than once per day won't change anything. Google updates the list of devices it's rolling out to only once a day.

 

Your best bet is to flash the factory image (skipping userdata) if you're unlocked. Or wait until someone posts the OTA URL and flash it manually. The latter is equivalent to receiving the OTA from Google. If the URL isn't up by now, it should be later today.

 

That being said, Marshmallow is definitely smoother. It could be an illusion from the new animations, but so far I'm liking it better.

 

Sent from my Nexus 6

 

 

So, on mobile, I use Chrome in desktop site mode for full S4GRU.

 

How? I haven't found a way to force the desktop version on mobile. Selecting "request desktop site" in Chrome just reloads the mobile version.

 

Sent from my Nexus 6