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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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