- Aug 30, 2012
- 143
- 0
- 0
Hi all! I am having an issue where my Pixel photos and videos appear to be counting against the 15 GB storage quota tied to Gmail, Drive, and Google Photos not taken or uploaded by a Pixel phone. This caused me to reach my 15 GB storage limit and delete photos and files from Photos and Drive. Has anyone experienced or found a remedy to this problem?
It just so turns out that this problem is unsolvable at the moment, according to support. I called Pixel technical support and they were ultimately unable to remedy the issue. It was a highly disappointing call, because technical support claimed this was an issue with Google Drive and/or Google Photos that they did not have experience dealing with. Their "fix" was suggesting that I compress my photos to high quality. To their credit, they did pledge to work with me to try and fix the issue over time, but it was disappointing that Google was unable to live up to its promise.
Gmail and Drive do not take up beyond 2 GB of storage, and prior to buying the Pixel in November, I had used Google Photos but never before run out of storage. On Google Drive, when I click on "Google Photos" and click the information icon next to a photo, it ironically says that it counts toward 0 bytes of my storage quota. And this is not just for photos taken on my Pixel either: all photos, screenshots, and other device photos count toward 0 bytes, including those taken/uploaded on my Nexus 6 and Nexus 6P. On Google Photos, it correctly states that I have unlimited storage at original quality. And yet, on the Google Drive storage page, it says that I have reached the 15GB limit, overwhelmingly from my Photos. And when I reach the limit, it will affect my ability to receive emails, which is a bit worrisome.
However, I made the point to Support multiple times that Google has promised Pixel users unlimited storage at original quality. I've now had several Pixels (one stolen, one lost, and one manufacturing defect) since November, but they've always been Pixels. I was very disappointed that Support admitted that there was no fix for this issue and they couldn't help. In the grand scheme of things, this is not a big issue, but it strikes me as a worrisome glitch/error that might not have a proper solution.
Let me know if anyone has experienced anything like this. Know I can always count on A/C for help! Thanks.
It just so turns out that this problem is unsolvable at the moment, according to support. I called Pixel technical support and they were ultimately unable to remedy the issue. It was a highly disappointing call, because technical support claimed this was an issue with Google Drive and/or Google Photos that they did not have experience dealing with. Their "fix" was suggesting that I compress my photos to high quality. To their credit, they did pledge to work with me to try and fix the issue over time, but it was disappointing that Google was unable to live up to its promise.
Gmail and Drive do not take up beyond 2 GB of storage, and prior to buying the Pixel in November, I had used Google Photos but never before run out of storage. On Google Drive, when I click on "Google Photos" and click the information icon next to a photo, it ironically says that it counts toward 0 bytes of my storage quota. And this is not just for photos taken on my Pixel either: all photos, screenshots, and other device photos count toward 0 bytes, including those taken/uploaded on my Nexus 6 and Nexus 6P. On Google Photos, it correctly states that I have unlimited storage at original quality. And yet, on the Google Drive storage page, it says that I have reached the 15GB limit, overwhelmingly from my Photos. And when I reach the limit, it will affect my ability to receive emails, which is a bit worrisome.
However, I made the point to Support multiple times that Google has promised Pixel users unlimited storage at original quality. I've now had several Pixels (one stolen, one lost, and one manufacturing defect) since November, but they've always been Pixels. I was very disappointed that Support admitted that there was no fix for this issue and they couldn't help. In the grand scheme of things, this is not a big issue, but it strikes me as a worrisome glitch/error that might not have a proper solution.
Let me know if anyone has experienced anything like this. Know I can always count on A/C for help! Thanks.