mrrogers1

I almost never delete entire conversations, but I do see the value in it for some things, like automatic notification threads. I also hate the insistence on archive instead of delete. Who thought that was a good idea? If I want it gone, I want it gone!

 

Yeah, archive means (I have a strong hunch) that they can still mine that data for their purposes even though it's use would surely be anonymized and never made public.  I did notice that you can dump the whole conversation IF you delete every message in a thread but that would be painful, as it stands, if you wanted to actually dump the whole thing and had a crap load of messages in the thread. 

Press and hold a message for a pop-up with a delete option. For a voicemail, tap to expanded, the tap the three dots in the lower left corner of the expanded message area, and there is a delete option.

 

 

This will let you delete "a" text but I think he (and I know I) was referring to deleting a whole SMS/MMS thread which makes the most sense (to me) from a end user stand point BUT yes, what you said definitely does work. 

 

Okay....so I got the Google Voice update yesterday. I do like the looks of the new GUI, however, there are a few things that frustrate me. 

 

For one, I not find a way to delete old Text Messages. I have look on both the Android App and the Chrome app neither one seem to have a way of deleting text messages or vociemails.

 

Granted it might be there somewhere, but if it is, I cannot find it, anywhere. 

 

Well, for now, the only way I found was going into the web app settings, click to go back the "Legacy Google Voice app" and delete from there.  Hopefully just a miss on Google's part.... I imagine they'll make a PITA to delete vs archive just like the Google Messenger app BUT it should be doable from the message list.  Hell, I wish they'd add the ability to swipe to delete (just like the Gmail app) to BOTH the Messenger and now *new Gvoice app but you know, they do love our data.

I smashed by Nexus 6P screen yet again. Face down, on asphalt. Prominent piece of gravel on top of the asphalt hits screen upon contact. Smash.

 

I had the original screen three days, then smash it. Keep the phone on a shelf for a year. Replace the screen, and use it for 6 weeks and smash again.

 

I've never had this problem before. Every time I drop this thing, it goes face down. It was in a good case, but face down just ain't going to save this thing. Maybe it's the weighting? Nah, I just an idiot.

 

Using Tapatalk on Note 8.0

 

Damn Rob

 

Well, if/when you repair it, again, I HIGHLY suggest and recommend good glass screen pro. I have used Intelliglass https://www.intelliarmor.com/shop-by-device/nexus-6p.html since day one (well, as soon as they were available) and while I haven't needed it to completely save my 6P, I have got a couple replaced by them after saving various devices from nasty drops. It would have (pretty positive) actually saved both your screens AND I can tell you the Intelliarmor product is top notch. I use the Max coverage (2 pack). 

Third carrier has been shown for quite sometime. Looking for confirmation of 2xCA without root

Damn, owell, that, I do not have confirmation of. Sorry for the confusion.

What is your point of the screenshot...?

 

Just showing 3rd carrier on B41 in SCP with no root.  Others were asking if anyone with 6P had picked it up and the screen shot the had been provided was with a different app and with root to get all the good logging info. 

Nexus 6P 7.1.1

 

 

Sent from my Nexus 6P using Tapatalk

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? 

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. 

This is what I'm dealing with...

 

Looks like it's a known issue

https://code.google.com/p/android/issues/detail?id=226039&q=Do%20not%20disturb&colspec=ID%20Status%20Priority%20Owner%20Summary%20Stars%20Reporter%20Opened

 

 

Sent from my Nexus 6P using Tapatalk

 

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 

Looks like it's a known issue

https://code.google.com/p/android/issues/detail?id=226039&q=Do%20not%20disturb&colspec=ID%20Status%20Priority%20Owner%20Summary%20Stars%20Reporter%20Opened

 

 

Sent from my Nexus 6P using Tapatalk

 

Ha ha! So yes, yes I actually did see the behavior as shown in the issue tracker. I hadn't had my normal schedule to anything wrong BUT after thinking about it, I have seen my DND on when I didn't think I actually turned it on.  

Anyone on the 7.1.1 beta having issues with DND not automatically turning itself off?

 

No issues with that here but my Hangouts v13 is being  real battery hog (as in 10% of battery used).  I just cleared data to see if that helps but Hangouts, in general, web and mobile has been RATHER buggy the last two days. I'll pay attention to DND though and see if there are any issues. 

All great info there, thanks for sharing.  ordered a new car charger today to get the "Rapid Charging" on the go, need to get a new charger for the office too

 

What I did to avoid buying a bunch of new chargers was use the OEM charger in the living room, where I would want the max charge rate since I'd most likely be plugging in just to top off or something.  Then I put one of my old QC2.0 chargers in my bedroom where I don't care how fast it charged since it would have 4-8hr to charge while I was sleeping. 

Doing some Ampere comparisons, my MXPE typically charged in the 3100-3300mah with i think 3600mah as a max, on the N6P, I've seen a max of 3050mah and it is typically in the 1800-2300mah charging range.  Watching the phone charge right now its been stable at 1950mah which is the current max with a min of 1160mah.

 

The charge profile can be different from one QC device to another and your MXP does charge faster 0 - 100% but the battery size is probably the gap. I can't find the chart but there was a good one where it showed a charge mah graph and it was quit interesting to see how some where VERY steep and then fell off while others where steep but stayed very steady up to the last 10%. To do a better comparison, you'd want to do a side by side from the same battery level and charge for x number of minutes and see what battery level is. 

 

If you go here http://www.phonearena.com/news/Phones-with-quick-charge-the-fastest-charging-from-0-to-100-2016-edition_id81675 you can see comparisons of the top phones for 2016 but you can also add in the MXP (bottom of the chart) which I did and it scores a 76 which is great but given the smaller battery size, I don't think it really matters but there isn't much else going on with our 6P's so why not.

 

Here is a good read and from what I can tell Moto tweaks their charging profile different than most. http://www.androidauthority.com/which-phone-charges-the-fastest-660181/  You can also see the profile for the 6P which just gives a visualization of what we already know. 

Having this device for just over a week and all my reviews are very positive except the lack of Miracast and QuickCharge 2.0.  Band switching is very fast, on par or faster than my Moto X Pure Edition.  This thing loves Band 26 and stays on it in many places that I would drop to to 3g or 1x.  Data sessions are much more stable, on the MXPE, many times I would have an icon for an LTE connection, but data would never actually flow.  The bump for the camera is much smaller than I expected and not an eye sore at all.  I love Android N and the Finger Print scanner for unlocking.  I can't wait for more apps to integrate finger print authentication.

 

Why are you missing QC2? IIRC, USB-C charges faster than QC2 though it's been awhile since I measured charge voltage on my 6P, I was pretty concerned about it too when I first got it back when it first came out. 

My panties are bunched.... Oh wait. :-D

True, it will be good enough to continuously upload pics to Google Photos. I'm hoping that our 6P shares some Italian carriers LTE bands so I can swap out the Fi SIM for the Italian carriers SIM for some LTE help with those pics.

I'd think you would rather upload on wifi as data would be burned through pretty quick (I'd think) uploading over mobile data, no matter the speed. That, and wanting to conserve batter for the travels and ability to take more pics.

 

Sounds like a fun trip regardless, congrats!

 

Sent from my Nexus 6P using Tapatalk

Latest on N is 3.64

 

Thanks! I'm on beta now and aside from needing to clear data for Hangouts, it's be problem free so far and Hangouts is MUCH better after clearing the old cached data out. I cleared my GSam Battery stat data so I can see how the battery is really holding up and today we'll see how the phone holds up on a "normal" work day.  So far, so good on all things but I'll try to report back in a few days so if anyone is still on the fence, they can take the plunge. 

For anybody interested, just installed Android N beta. It is running quite smoothly. Battery life has improved as well. So far seeing a bit over 4 hours screen on time with heavy use.

 

I've fallen in love with my N6P once again, Android N is a sweet upgrade!

 

Also seems that the baseband is updated as well. I have not gone out to test the radio performance, but so far its good.

 

FYI: From my findings radio 2.15 has been the best at holding B41.

Thanks for sharing, and thanks to everyone else above that did so as well.

Si ce you mentioned you think the 2.15 radio is best for B41, can you post what radio is packaged with the N beta?

Any thoughts/experiences on battery life when using wifi + airave, vs wifi calling w/o airave?

 

Sent from my 0PJA2 using Tapatalk

 

My experience has been wifi calling is a battery hog though I haven't used a M9 or another wifi calling device on Marshmallow so maybe they changed that... 

Just voice, no video. It was someone who called me on my Google voice number.

 

If you just want Hangouts over wifi but not LTE, you need to use two separate numbers, correct?

 

And yeah, the network may be better where you are. In San Francisco and Oakland if you're not on B41, you're looking at speeds of around 0.2 mbps.

 

Sent from my Nexus 6P

 

I'm not following on the someone calling your Gvoice number as it should ring your phone, not the Hangouts app. That sucks to hear about San Fran/Oakland, I can't imagine. 

Eh, Hangouts/Gvoice really struggles on B26 (and in SF Sprint seems to prioritize B26 over B25 for some reason...). Last night for example I had a good signal, but on overloaded B26, which is the norm. The call was garbage, all broken up. I couldn't understand a thing. If it had been a regular call over 1x it would have been fine.

 

Basically, I don't trust Hangouts/Gvoice to work reliably on LTE unless you're on B41.

 

It also makes me wonder how well VoLTE will work whenever it's rolled out... I guess they would do some sort of QoS to try to prevent that from happening on overloaded sectors. But still...

 

Sent from my Nexus 6P

 

Hangouts video call OR are you talking voice call via Google voice? Reason I ask is "wi-fi calling" was in question, so we were talking about a solution to "wi-fi calling" which only happens on wifi.  If you have LTE, wouldn't you just use your phone to make the call? 

 

To add, while I can carry on video with voice over all LTE bands here, without issue, as always, our experiences are subject to our local. 

And Wi-Fi Calling. And LTE roaming.

 

Wi-Fi calling = Gvoice and roaming, whats that? 

 

(*and before ANYONE goes on a tirade about how it's not the same, YES, I KNOW it's not the same as Sprint  wi-fi calling but it is a solution that works quite well, if not better IMHO.  Sprint's wi-fi calling implementation is a HUGE battery hog for some strange reason even when not in use.  I don't miss it one bit.)

Is it still worth it to purchase a Nexus 6p? Also I'm coming from the Moto Nexus 6.

 

Sent from my Nexus 6 using Tapatalk

 

I think so, I still REALLY am enjoying everything about mine and nothing out there NOR on the horizon really intrigues me or can do anything the 6P is doing, better.   Spigen Tough Armor + Intelliglass screen pro

After reading this thread, i checked and got this notice. See attached photo

Not sure I want to do this as job software may not be ready for this.Screeenshot 2016-02-17 HTC M9 Upgrade notice.png

 

Is "job software" for Remote Administration or an app you have to use to actually do your job?