Jump to content

Google Nexus 6 by Motorola Users Thread


WiWavelength

Recommended Posts

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

Link to comment
Share on other sites

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

A lot of these things can be fixed in SCP. Post what you're seeing in that thread and the developer can work through them. Had similar issues with Lollipop.

 

However, on my N5, Marshmallow and SCP seem to be co-habitating well. So far...

 

Using Tapatalk on BlackBerry Z30

Link to comment
Share on other sites

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 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

Link to comment
Share on other sites

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

 

The LTE issues can likely be worked around when hunting LTE by using a "terminal emulator for android" by Jack Palevich or similar product. Type in "ping -c99999 8.8.8.8"  and let it run while hunting LTE (ping uses almost no data).  If you are hunting 1x1900 or 1x800, then ping should be avoided as it can cause SID-NID-BID to stay locked on the first site.  

 

The '1x and LTE "bug" in SCP' more and more frequently does make the display almost worthless for many CA capable phones, but SCP does log correctly.  I recommend using Signal Detector or LTE Discovery to see the GCI when needed.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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...

 

Lenovo!

 

I called it.

 

;)

 

AJ

Link to comment
Share on other sites

 

THANK YOU!!! I've been waiting patiently instead of flashing it simply because I don't want to risk getting stuck in a boot loop or bricking my phone.

Link to comment
Share on other sites

...simply because I don't want to risk getting stuck in a boat loop or bricking my phone.

 

Yeah, you have to watch out for those boat loops.  They can be dangerous.

 

 

AJ

  • Like 5
Link to comment
Share on other sites

Sprint OTA to be completed by 10/23.

 

https://community.sprint.com/baw/message/1013767#1013767

 

I got the security update on the last day so let's see how long this one takes to get to me.

 

edit: I see someone said the same thing in response to that in the link.

Link to comment
Share on other sites

I got the security update on the last day so let's see how long this one takes to get to me.

 

edit: I see someone said the same thing in response to that in the link.

You have a Nexus 6 and you are waiting for an OTA?  I thought that was the whole point of a true Nexus device.  I'm loving 6.0 on the Nexus 6.  I'm getting great battery life as well!

Link to comment
Share on other sites

You have a Nexus 6 and you are waiting for an OTA?  I thought that was the whole point of a true Nexus device.  I'm loving 6.0 on the Nexus 6.  I'm getting great battery life as well!

 

I said it a few comments up. I prefer to not to flash ROMs or updates for fear that I'll get stuck in a boot loop or brick my device.

Link to comment
Share on other sites

I said it a few comments up. I prefer to not to flash ROMs or updates for fear that I'll get stuck in a boot loop or brick my device.

That's understandable I know you come from a long list of HTC devices like myself. It's painful dealing with soft bricks and boot loops. With Nexus devices its extremely difficult to brick your device. I usually flash stock rooted roms and delete all the unnecessary gapps that I don't use.

 

Sent from my Nexus 6 using Tapatalk

  • Like 2
Link to comment
Share on other sites

That's understandable I know you come from a long list of HTC devices like myself. It's painful dealing with soft bricks and boot loops. With Nexus devices its extremely difficult to brick your device. I usually flash stock rooted roms and delete all the unnecessary gapps that I don't use.

 

Sent from my Nexus 6 using Tapatalk

 

I said it a few comments up. I prefer to not to flash ROMs or updates for fear that I'll get stuck in a boot loop or brick my device.

I'm sorry I completely glossed over that comment.  I must agree with tybo31316, as flashing stock images on Nexus devices is much easier and better than HTC.  I remember having the original EVO and EVO 3D and how horribly annoying it was with those devices.  Either way, 6.0 has been running great.  Hope you get it soon.

  • Like 2
Link to comment
Share on other sites

I'm sorry I completely glossed over that comment. I must agree with tybo31316, as flashing stock images on Nexus devices is much easier and better than HTC. I remember having the original EVO and EVO 3D and how horribly annoying it was with those devices. Either way, 6.0 has been running great. Hope you get it soon.

6.0 is super smooth. I'm liking the animations. Seems like battery life and the new radio has improved too.

 

Sent from my Nexus 6 using Tapatalk

  • Like 1
Link to comment
Share on other sites

6.0 is super smooth. I'm liking the animations. Seems like battery life and the new radio has improved too.

 

Sent from my Nexus 6 using Tapatalk

I agree, battery life is much better.  I wish SCP worked consistently, but I think that is more of an issue with 6.0.

  • Like 1
Link to comment
Share on other sites

Anyone on Marshmallow having issues closing apps?  I use Audible, and I used to be able to go to recent apps and close it or use the X on its notification.  Now, even though it appears to close, and no longer has a persistent notification or shows up in the recent apps list, as soon as I get back in my Explorer and Sync connects, it begins playing the audio book I was last listening to.  The only way to stop it is to dig into the app info and hit the Force Stop button.  I've Googled a bunch to see if others are reporting this kind of problem, but I guess not that many people are on Marshmallow, yet, or it is unique to Audible.  Heck, it may be something in a recent update, that just happens to coincide with me changing over to the Nexus 6.

 

Thanks!

Link to comment
Share on other sites

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

  • Like 1
Link to comment
Share on other sites

I got my OTA yesterday. Appears to not like to hold on to B41 as much. Before I was holding on to it much longer and getting good speeds. Now I'm on B25 a lot more. On my normal running route I would be able to stream music perfectly, now it skips in certain spots where it's on B25 instead of B41. 

Link to comment
Share on other sites

I got my OTA yesterday. Appears to not like to hold on to B41 as much. Before I was holding on to it much longer and getting good speeds. Now I'm on B25 a lot more. On my normal running route I would be able to stream music perfectly, now it skips in certain spots where it's on B25 instead of B41.

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

  • Like 2
Link to comment
Share on other sites

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

 

I would glance at Signal Check Pro but didn't base any of my experiences on it as the developer said he hasn't updated it and others reported it not working correctly on 6.0. I've been running the same route for a while now and I can't remember a skip once until last night where it happened multiple times at different locations.

 

My route is approximately 5 miles and I know I come really close to at least two different sites that boardcast B41. I noticed the skips happen when I'm pretty much in the middle of the two sites (where B41 would theoretically be at its weakest). I'm thinking the new radio drops back to B25 quicker which I know is congested in my area based on previous tests. Again, I wasn't factoring in what Signal Check was currently reporting.

 

Just sharing my real world experience and assumptions based on previous tests a few months ago. I'm in northern Orange County, CA area for those interested.

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
    • "The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline June 1 for 850Mhz of mmWave in most of Ohio covering 27500-28350Mhz expiring 6/8/2028. No reported sightings.  Buildout notice issue sent by FCC in March 5, 2024 https://wireless2.fcc.gov/UlsApp/letterPdf/LetterPdfController?licId=4019733&letterVersionId=178&autoLetterId=13060705&letterCode=CR&radioServiceCode=UU&op=LetterPdf&licSide=Y&archive=null&letterTo=L  No soecific permits seen in a quick check of Columbus. They also have an additional 200Mhz covering at 24350-25450 Mhz and 24950-25050Mhz with no buildout date expiring 12/11/2029.
    • T-Mobile Delivers Industry-Leading Customer, Service Revenue and Profitability Growth in Q1 2024, and Raises 2024 Guidance https://www.t-mobile.com/news/business/t-mobile-q1-2024-earnings — — — — — I find it funny that when they talk about their spectrum layers they're saying n71, n25, and n41. They're completely avoiding talking about mmWave.
    • Was true in my market. Likely means a higher percentage of 5g phones in your market.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...