Correct, unfortunately, it's always been that way for me so I don't really know how to troubleshoot the issue.
Very strange. I'll try a reboot when I get home.
Correct, unfortunately, it's always been that way for me so I don't really know how to troubleshoot the issue.
Really? After you take a screengrab with power + down-volume button?
Hm. My Pixel doesn't seem to do this. Is there something I'm missing? Settings? I have to go to "Device folder" or "albums" in order to see it.
Anyone experiencing an issue with charging? Occasionally when I plug in to charge, it will fluctuate between charging and not charging. In order to fix this I have to reboot the device and then it's perfectly fine. This usually happens anywhere between 3-6 days of uptime, can't seem to get more than that. I'm hoping the December patch that released today might fix this; since a reboot fixes this I don't think it's a hardware issue.
I should have specified in my first post that I am also using the USB-C to USB-C cable with the official power brick as well. I've tried wiggling the cable and just letting it sit there but nothing except a reboot seems to fix it for me. So far so good with the new patch, but it hasn't been my usual 3-6 days of uptime so it's still early to tell. Hopefully this will fix it, but I'm glad that I am not the only one experiencing this.I have this problem, it seems to be only when I charge with the USB-C to USB-C cable in the official power brick. If I use the USB-C to USB-A in an Apple/Samsung brick it works no problem.
The problem I have is when plugged in sometimes it does nothing or sometimes it goes from charging to not charging, if I wiggle the cable at the phone end it starts charging again... Very weird.
I am installing the update now so will let you know if it fixes the problem.
I should have specified in my first post that I am also using the USB-C to USB-C cable with the official power brick as well. I've tried wiggling the cable and just letting it sit there but nothing except a reboot seems to fix it for me. So far so good with the new patch, but it hasn't been my usual 3-6 days of uptime so it's still early to tell. Hopefully this will fix it, but I'm glad that I am not the only one experiencing this.
I should have specified in my first post that I am also using the USB-C to USB-C cable with the official power brick as well. I've tried wiggling the cable and just letting it sit there but nothing except a reboot seems to fix it for me. So far so good with the new patch, but it hasn't been my usual 3-6 days of uptime so it's still early to tell. Hopefully this will fix it, but I'm glad that I am not the only one experiencing this.
anybody switch from iphone 7 plus to pixel xl?
i think same. how was it? worth it?
i came from note 7.. to iphone 7 plus.. im not interested with other android phone so i went back to iphone..
i love how fast iphone 7 plus is.. i have s7 but i hate how it lags even on typing ..
if pixel/XL is faster than s7 and doesn't lag after few months... im in...
Unfortunately the newest update didn't help, it took 2 attempts to get my phone charging last night... I might just have to use the USB-C to USB-A cable instead.
Please keep us up to date after 6 days. Curious to know more about this myself for my father's pixel. Hopefully update fixes it.
Thanks @epicrayban it is definitely an odd issue. Hopefully your father's Pixel won't have this issue. Mine did this within a week of having it but I was traveling so I wasn't able to deal with it and figured a reboot every 3-6 days isn't the worst thing for a device.
I contacted Google support through the settings app and was immediately connected to a chat representative. I explained the issue along with the workarounds (reboot or using the USB-C to USB-A cable) and he said he discussed with an expert and the expert suggested to have the device replaced. I'm following another site on this issue and a user there has already received a replacement for this issue, but the replacement device still has the same issue. So I opted to not get a replacement now as I can just use workarounds and hope that Google can fix this in an update. Because other than this charging issue, my phone is otherwise great and I'd hate to get a replacement that fixes this issue but has a different issue.
I should probably clarify that by contacting support my intention wasn't to get a replacement device, but rather to provide logs from the phone to pass along to the QA/Dev team to see if they would be able to determine why this is occurring and hopefully resolve in a future monthly update. However, it was very nice of Google to offer that!
Has anyone switched from a 6/6S/7 Plus to a Pixel (non XL)? Did the screensize feel like a huge downgrade? How is it compared to a non-plus iPhone?
I played with a Pixel XL at Best Buy yesterday and yup, same screen size as my 6S+. There wasn't a regular Pixel on display to try out. I would never downgrade to a non-plus iPhone as I find the screen too small, but I'm not sure I want to pay an extra $120 for the XL, not to mention the fact they're impossible to find. With the Pixel sitting somewhere between the non-plus and plus iPhones in screen size, I'm curious to see how it is.
Why is it so hard to change this phone to vibrate only? Where is the simple toggle for sound/vibration? Like the one in Touchwiz. Do not disturb doesn't seem to have a "set to vibrate only" option, does it?
Some things about Google's decisions are seriously questionable. And if there's no solution other than, press the volume down hardware key, and if it's not on the correct sound profile while you're doing that, you have to pull down the menu to get to the sliders, if that's the only way, it's downright idiotic.