Jump to content

Google Nexus 6 by Motorola Users Thread


WiWavelength

Recommended Posts

i thought wifi had to be off to do a prl update

Nope I've done it on wifi. I was going to a newer version so I definitely know it worked.

 

It's too bad there isn't a way to manually write a PRL like on some other phones.

 

Sent from my Nexus 6

Link to comment
Share on other sites

So is band 26 rf as strong as band 25 or the same.i thinking jumping ship soon , so done with samsung notes.

Its about the same. Nexus 6 hold band 25 like no phone before it. Band 26 is really good too. I would say its the same.
  • Like 1
Link to comment
Share on other sites

Got the factory image last night. Stagefright free now.

And a single release for all mobile providers, unlike 5.1.1 where T-Mobile and Fi users received individual branches. Nice and simple.

 

-Mike

  • Like 1
Link to comment
Share on other sites

And a single release for all mobile providers, unlike 5.1.1 where T-Mobile and Fi users received individual branches. Nice and simple.

 

-Mike

I noticed volte is still here but wifi calling is gone for T-Mobile.

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

Got the factory image last night. Stagefright free now.

I updated to the newest release LMY48i. I messed around and got encrypted again. My device ran just a tad bit slower but the battery life difference was major. I ended up decrypting again now my battery life is back to normal.

 

Sent from my Nexus 6

Link to comment
Share on other sites

I updated to the newest release LMY48i. I messed around and got encrypted again. My device ran just a tad bit slower but the battery life difference was major. I ended up decrypting again now my battery life is back to normal.

 

Sent from my Nexus 6

I don't know what's up with battery life and encryption. Maybe it's because it has to do more.

 

Sent from my Nexus 6 using Tapatalk

  • Like 2
Link to comment
Share on other sites

I don't know what's up with battery life and encryption. Maybe it's because it has to do more.

 

Sent from my Nexus 6 using Tapatalk

Does not updating the boot loader when upgrading the radio cause the radio to not function properly? The reason I ask is because normally I don't upgrade the bootloader just the radio when flashing updates ROMs. When I flashed the latest ROM with the stage fright fix I upgraded the bootloader. Now I've noticed that my Nexus 6 hangs on the LTE longer and it rescans for LTE connection faster. This is using the same radio just with an upgraded bootloader.

 

Sent from my Nexus 6

Link to comment
Share on other sites

No its not. Then again it's not final. It feels more like Android 5.5 rather than 6.0

 

Sent from my Nexus 5 using Tapatalk

There is some new things. Look at the signal icon when it is switching networks.a9b7bb3943382eb991f3656f06cc6e6b.jpg

 

Sent from my Nexus 5 using Tapatalk

  • Like 4
Link to comment
Share on other sites

I have been noticing substantial on screen time with this preview. I didn't want to post it here unless it was consistent and I have been getting 5 hours minimum of on screen time after this build. In the 3 days I have been testing it. This is stock and encrypted btw. fa1681ac6eb7989d7310c065765573f3.jpg

 

Sent from my Nexus 6 using Tapatalk

  • Like 7
Link to comment
Share on other sites

I have been noticing substantial on screen time with this preview. I didn't want to post it here unless it was consistent and I have been getting 5 hours minimum of on screen time after this build. In the 3 days I have been testing it. This is stock and encrypted btw.

 

Sent from my Nexus 6 using Tapatalk

Wow, that battery life is incredible!

  • Like 1
Link to comment
Share on other sites

Those having missed incoming calls when connected to WiFi and LTE.

If users don't report this issue this will never get resolved, call sprints executive # and report it. Be very specific, let them know when WiFi and LTE are connected at the same time.<br />

The phone # on the better business bureau website will get you to executive customer service.

http://www.bbb.org/kansas-city/business-reviews/telephone-communications/sprint-corporation-in-overland-park-ks-98010534/

Sent from my Nexus 6 using Tapatalk

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

I wonder how the 2015 models will compare to the 6

 

Sent from my SPH-L720 using Tapatalk

I think we both will be great phones but I'm not interested in either one. I'm still satisfied with my Nexus 6.

 

Sent from my Nexus 6

  • Like 2
Link to comment
Share on other sites

Not sure if this has already been brought up but is anyone else experiencing burn-in on the top and bottom of their N6?

IIRC the N6 uses an AMOLED screen, so that's normal. (And it's the reason I prefer a nice LCD over an AMOLED. I love the recent Moto hardware design, but AMOLEDs really make me question it.)
Link to comment
Share on other sites

IIRC the N6 uses an AMOLED screen, so that's normal. (And it's the reason I prefer a nice LCD over an AMOLED. I love the recent Moto hardware design, but AMOLEDs really make me question it.)

 

The 2015 Moto X Style/Pure Edition display is LCD.

 

AJ

  • 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

    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 
  • Recently Browsing

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