Jump to content
jefbal99

Google Nexus 6P by Huawei (was [Rumor] Huawei Nexus phone?)

Recommended Posts

I'm going to post in there again as I have noticed that as soon as I initiate a phone call, my phone is activating DND now. If I change the "Sound" setting to speaker or bluetooth, it goes off but if it's on phone, its on DND.

 

Really weird

It's a feature. However I can't get it to work on my phone. I actually wish it would go to DND mode while on a call. People on the other end of the call can hear my phone vibrating.

 

Sent from my Pixel XL

Share this post


Link to post
Share on other sites

Got the 7.1.1 preview update tonight, hopefully fixes the DND issues

 

Sent from my Nexus 6P using Tapatalk

  • Like 1

Share this post


Link to post
Share on other sites

This is what I'm dealing with...

 

ae37163aa4579b83170f6b4bb1b4c418.jpg

  • Like 1

Share this post


Link to post
Share on other sites

I use hangouts on a daily basis for work for both texts and phone calls. That is the percentage I typically hit when I use it for work. I am using it on 7.1.1 preview as well. Obviously I am not having the problem. I have uninstalled and reinstalled all apps after changing to 7.1.1 though. The biggest problem I have had is with Chrome. Before the last preview update, chrome would often become unstable and crash the phone.

 

This is what I'm dealing with...

ae37163aa4579b83170f6b4bb1b4c418.jpg

Share this post


Link to post
Share on other sites

I use hangouts on a daily basis for work for both texts and phone calls. That is the percentage I typically hit when I use it for work. I am using it on 7.1.1 preview as well. Obviously I am not having the problem. I have uninstalled and reinstalled all apps after changing to 7.1.1 though. The biggest problem I have had is with Chrome. Before the last preview update, chrome would often become unstable and crash the phone.

 

So you "are" or "are not" having that problem because I think you "are" if the battery percentage used is like mine. Or. maybe the screen really isn't as much of a hog as one would typically see.  It's just very strange that the app, in and of itself can use double the battery that the screen is using.  If this is proving to be normal for med/high Hangout users, then maybe I just need to recalibrate my expectations.  I've just never see anything like this before and not sure how the app is burning so much power on it's own and still functioning how it should. 

Share this post


Link to post
Share on other sites

Thanks to Skid71's suggestion, I finally have my Nexus 6P repaired. A year after destroying it. Still feels like a brand new phone after all this time!

 

Huawei offered me a $30 coupon at check out. Ended up costing around $130 total for screen replacement and shipping.

 

:thx:

 

Robert,

I lack the vision and skill to repair my own screen, but shipped it to Texas through Huawei to get it repaired. Made me sick when I busted it. Live and learn, I'll bite the bullet and build the cost of nexus protect into my next nexus purchase.

If memory serves $160. Which made me even more angry at myself. First phone I've ever broken. Laid it on top of the garbage can in the garage while I was working. Forgot it was there, flipped up the lid and it went for a 20 foot ride in the air across the garage.

Sick

Just sick

I'm sick to my stomach. I just destroyed my 6P. I had it on the center console of my pickup just now. I discovered a Tmo site that just started work so I pulled off the road quickly. Phone slid into the back of my crew cab. No big deal.

 

I hop out to go open the back door to get it. I guess it was on the floor against the back door, because when I opened the door, it slid out and landed on the rough asphalt face down.

 

I freak out and pick it up and there really is no physical damage except a little scrape on the frame and a scratch on my glass screen protector. But the display is no longer working. :'(

 

I now have a $600 paper weight. I feel like I'm going to throw up. I cannot afford to replace it. I had to sell phones to buy it. I guess I just can't have nice things.

 

b8c39f07c90a4110e1de55af82da078a.jpg

 

Sent from my Nexus 5 using Tapatalk

 

 

Sent from my Nexus 6P using Tapatalk

  • Like 3

Share this post


Link to post
Share on other sites

Has anyone ever had a confirmed B41 2x CA connection on the 6P?  My coworkers Samsung is always on 2x CA from the site near our office, however, I can't find anything in the DATA screens that even indicates CA is enabled.  LTE Engineering is worthless on this device.  LTE Discovery is only showing a single EARFCN/Frequency range.  Speed tests are usually in the 20-30 Mbps range, which is more than usable, but they are very similar to the results I got on my Moto X Pure previously.

Share this post


Link to post
Share on other sites

Has anyone ever had a confirmed B41 2x CA connection on the 6P?  My coworkers Samsung is always on 2x CA from the site near our office, however, I can't find anything in the DATA screens that even indicates CA is enabled.  LTE Engineering is worthless on this device.  LTE Discovery is only showing a single EARFCN/Frequency range.  Speed tests are usually in the 20-30 Mbps range, which is more than usable, but they are very similar to the results I got on my Moto X Pure previously.

Have you tried Network Signal Guru?  That is what we use locally to confirm B41 2x CA.  Root provides you with the most information.

Share this post


Link to post
Share on other sites

Have you tried Network Signal Guru?  That is what we use locally to confirm B41 2x CA.  Root provides you with the most information.

 

I've not rooted this device or my MXPE, the extra SCP info is the only thing I've missed.

  • Like 2

Share this post


Link to post
Share on other sites

I've not rooted this device or my MXPE, the extra SCP info is the only thing I've missed.

Rooting on the 6P is sooo easy.  I agree, I do not use it for much though...

Share this post


Link to post
Share on other sites

Rooting on the 6P is sooo easy.  I agree, I do not use it for much though...

I've got the boot loader unlocked, but I don't want to alter the system image to root.  I've been doing the Android beta program and don't want to risk breaking one of those updates

Share this post


Link to post
Share on other sites

Has anyone ever had a confirmed B41 2x CA connection on the 6P? My coworkers Samsung is always on 2x CA from the site near our office, however, I can't find anything in the DATA screens that even indicates CA is enabled. LTE Engineering is worthless on this device. LTE Discovery is only showing a single EARFCN/Frequency range. Speed tests are usually in the 20-30 Mbps range, which is more than usable, but they are very similar to the results I got on my Moto X Pure previously.

I have and am providing screen shots from NSG confirming it.

 

444f87cc1fba99c41a2423ce5bccfa92.jpg

 

It even shows the throughput on each carrier (this was during a speed test).

 

Sent from my Pixel XL

  • Like 4

Share this post


Link to post
Share on other sites

I have and am providing screen shots from NSG confirming it.

 

[image Remove]

 

It even shows the throughput on each carrier (this was during a speed test).

 

Sent from my Pixel XL

 

Is that your Pixel or 6P? 

Share this post


Link to post
Share on other sites

I have and am providing screen shots from NSG confirming it.

 

It even shows the throughput on each carrier (this was during a speed test).

 

Sent from my Pixel XL

Maybe because I don't have root, but I can't get any information from the NSG app

Share this post


Link to post
Share on other sites

Maybe because I don't have root, but I can't get any information from the NSG app

 

You need root to get a lot of the in depth info for NSG. 

  • Like 1

Share this post


Link to post
Share on other sites

I've got the boot loader unlocked, but I don't want to alter the system image to root. I've been doing the Android beta program and don't want to risk breaking one of those updates

You don't have to. After unlocking, flash TWRP using fastboot and then flash SuperSU. You can then run rooted programs like Network Signal Guru. Never have to modify your system image. That's what I'm doing. That way I can monitor CA.

 

Sent from my Nexus 6P using Tapatalk

  • Like 2

Share this post


Link to post
Share on other sites

You don't have to. After unlocking, flash TWRP using fastboot and then flash SuperSU. You can then run rooted programs like Network Signal Guru. Never have to modify your system image. That's what I'm doing. That way I can monitor CA.

 

Sent from my Nexus 6P using Tapatalk

Even on 7.1.1?

Share this post


Link to post
Share on other sites

Is that your Pixel or 6P?

It's an older screenshot from my 6P. You can tell because the nav buttons are hollow. On the Pixel they're solid.

 

Sent from my Pixel XL

  • Like 2

Share this post


Link to post
Share on other sites

Even on 7.1.1?

I think you can use FlashFire (from Chainfire, the developer of SuperSU) to install the OTA. That will let it apply cleanly with root, and then reroot you after. But you should check the FlashFire thread if XDA just to be sure.

 

Sent from my Pixel XL

Share this post


Link to post
Share on other sites

You don't have to. After unlocking, flash TWRP using fastboot and then flash SuperSU. You can then run rooted programs like Network Signal Guru. Never have to modify your system image. That's what I'm doing. That way I can monitor CA.

 

Sent from my Nexus 6P using Tapatalk

it's been awhile since I rooted, but flashing SuperSU from recovery placed the su binary and other files in /system or has that changed?

 

Sent from my Nexus 6P using Tapatalk

Share this post


Link to post
Share on other sites

Perhaps I'm misreading LTE discovery. 54f610f3e37a95e865ca79e342fddcce.jpg

 

I thought the EARFCN channels and frequencies were the ranges, but now I'm thinking it's the two channels and this is showing CA.

 

Thoughts?

 

Sent from my Nexus 6P using Tapatalk

Share this post


Link to post
Share on other sites

Perhaps I'm misreading LTE discovery. 54f610f3e37a95e865ca79e342fddcce.jpg

 

I thought the EARFCN channels and frequencies were the ranges, but now I'm thinking it's the two channels and this is showing CA.

 

Thoughts?

 

Sent from my Nexus 6P using Tapatalk

That's the channel/frequency range that your band 41 connection could be.

 

Sent from my 2PYB2 using Tapatalk

Share this post


Link to post
Share on other sites

That's the channel/frequency range that your band 41 connection could be.

 

Sent from my 2PYB2 using Tapatalk

Reason I was thinking it was two different channels is the carriers are only 20mhz wide, the two frequencies listed are 194 Mhz apart

Share this post


Link to post
Share on other sites

Reason I was thinking it was two different channels is the carriers are only 20mhz wide, the two frequencies listed are 194 Mhz apart

Band 41 is 194MHz in total. 2496 MHz to 2690 MHz.

Share this post


Link to post
Share on other sites

Nexus 6P 7.1.1

 

11e4a2e5b3b5e8c2c8ae11a2e6136d85.jpg

 

Sent from my Nexus 6P using Tapatalk

  • Like 2

Share this post


Link to post
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

  • Similar Content

    • By nexgencpu
      First Pixel device im somewhat excited about in a quite a while..
       
    • By Nrbelex
      The rumor mill has fully geared up, so it seems time for a thread in which the potential HTC-made 2016 Nexus phones can be discussed.
       
      Rumors suggest two phones: a 5" device codenamed Sailfish, and a larger device codenamed Marlin. Both are thought to be produced by HTC. [There's also a report that Google is making its own phone, without an OEM partner--along the lines of a Pixel phone--but that report has been largely discounted.]
       
      Android Police has claimed it knows with 8/10 certainty some specs of the smaller device--Sailfish:
      Manufactured by HTC 5" 1080p display (~440PPI) Quad-core 2.0GHz 64-bit processor (model unknown) 4GB RAM 2770mAh battery 32GB storage (unknown if multiple models will be available, or even if this is the base storage level) 12MP rear camera, 8MP front Rear-mounted fingerprint scanner USB-C port (bottom) Bottom-firing speaker or speakers (unknown if dual) Top-mounted headphone jack Bluetooth 4.2 Any thoughts on these devices? The last several Nexus devices have been Sprint compatible; is there any reason to think these won't be? Any hints in regulatory filings? How is HTC's radio performance, generally? Will Sprint sell them directly, and even if they do, will it still be preferable to buy directly from Google?
    • By nexgencpu
      Hopefully we can finally start seeing some user feedback. So far so good! it is without a doubt the best device ive owned!!!
    • By topdownat4
      Had not seen a thread for this yet, 
      I see some definite consumer advantages with Sprint's Network combined with TMob and Wi-fi.
      I have had many Nexus devices and I love my Nexus 6, although it is a bit big.
      The price is good for the service. ($20 / unl talk/txt, $10/gb)
       
      I hope the technical aspects work as they propose. I am a Google Voice Number user and love the "Any device" call capability and use it on my Tablet, Chromebook and phone. I rarely actually answer my Phone at the house. Answer the tablet or Chromebook.....
       
      I love Sprint's network, the upgrades they are putting forth and this Site, but if Project Fi works as advertised, it might lure me to sign on.....
       
      What are everyone's thoughts?
       
       
       
       
  • Posts

  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...