Interesting, thank you for the detailed response. The Pixelify github (the official "Kingsman44" one, not the BaltiApps "Google Photos" one) does specifically mention the ability to upload in original quality, but you need to do some extra stuff to get that working with "Zygisk" or "Riru". Did the devs make it so that it actually only works for high def anyway, not original?
It's been a while since I've kept up to date with the original Pixelify, but that had not been an option/feature about 2 months ago! I guess enough users pestered the devs about it (I myself left a post here on their XDA thread about it). I remember there was an automated response on their Telegram addressing it with the explanation that they didn't want to push it with Google as it's more believable that Pixel 5's were still uploading than the OG Pixel from '16...
It doesn't give in Github, but I am curious how to get that particular feature working with Zygisk or Riru specifically. In any case, again, I've run into a couple of cases that that module wrecks a lot of Pixel native set up (I imagine because it may be "doubling up" on code and features), so if you employ a Pixel, it may not be the best of ideas and/or you should be aware of that possible issue; I believe Pixelify is there mostly to offer the "Pixel" experience to other devices...
I actually ordered a second hand, original Pixel first gen from ebay (starting to regret that now), though I also wanted to try to make it work on my every day non-pixel phone.
That might be a good idea (and/or the idea many are having that are trying to make use of the "feature" while it's available) that many are having -- the thought being that you take photos from whatever device, manually export them to the OG Pixel, then have the Pixel "backup" or upload it to your Google Photos account from the device and it wouldn't count against your storage capacity but still be original quality and done in a legit way. I did the same thing when I had my Pixel 2 XL (and they were offering the feature) and loaded all my digital pictures from my digital camera and it's all there without using up my storage allotment.
My thinking is that Google imagines that the OG Pixel had such a limited camera hardware & capacity that anything taken from it -- even in 2023 -- wouldn't really take up much space, so they've left it as the only device to have the unlimited backup at original quality.
If google actually starts banning people for using the original upload for the first gen Pixel phones, or retroactively made all their pictures/media count against their storage allowance, they'd also catch legit Pixel users in the crosshairs. And they might open themselves up to legal action for breaking their original sales promise and punishing users for using it (though I'm sure they have a "we can do whatever we want anyway" clause). And do they actually care that much about a few thousands of users using that when their infrastructure is set up to handle billions of users?
You say that, but that's exactly what they've done from the Pixel 5...
Their advertisement and reasoning was that, because they weren't offering external storage (like the Samsungs at the time as well as other manufacturers), that if they offer unlimited storage at original quality of what usually takes up the most space on a smartphone (and also since they have their own app/service; Google Photos), it'll justify not having the option at the external storage. But while I was using the Pixel 5, they had backtracked and changed that "feature" -- which incidentally made me really question and hesitate getting a Pixel if they didn't offer it -- that from Pixel 2-5, it'll only be unlimited at Storage Saver quality and not even offered at all on the Pixel 6 or 7 (and presumably anything after). So if they retroactively changed it from the Pixel 2-5, I'm sure they wouldn't put too much of a fret for changing it to the Pixel 1; and/or I wonder how much legal liability would they have on the matter.
And although there would only be a couple of thousand users -- both legitimately using OG Pixels as a workaround and those using Pixelify -- if you think about it, how many GB and potentially TB of full quality photos and videos, after a couple of years, especially as smartphones get higher quality hardware (what is the MP of the main lens on S23 and iPhone 15?) as well as if the method spreads further and further...? I'm sure it will stress their servers a good amount that it will be flagged by the higher-ups...
As far as I know, compression only happens when pictures are over 16 MP and videos are over 1080p (
source). For most users, or for most pictures and videos, Storage Saver quality is good enough. I would personally be happy with that.
I don't think they will deactivate accounts or remove the media files without warning. But I do expect them to plug this loophole/ exploit going forward.
I have heard Pixel Experience ROM and some other custom ROMs have this option built in. Is that true? Does installing one of these custom ROMs allow unlimited uploads in Storage Saver quality WITHOUT ROOT?
You're most likely right about the when the compression only happens, but if you read it literally, it just states "Photos are compressed to save space. If a photo is larger than 16 MP, it'll be resized...", which implies (or if literally taken) means Photos are compressed -- as in all photos are compressed -- but those that are larger than 16MP will be resized to max 16MP...
But you're reasoning is why I accepted it on the Pixel 5 (while also the Pixel 5 did not boast any impressive camera hardware or post processing skills) that most photos and videos at that quality should be acceptable -- I was more mad and miffed that they refuse the option for external storage and offered this "feature" as a compromise just to limit and take it away...!
Like I said, "
at worst" would they deactivate accounts, remove photos/videos, and/or cause those to start counting -- I mean, if you think about it, it wouldn't be that hard since every digital photo has the device/camera used in the metadata, so they could just flag those under the spoof "Pixel 1" and either mark it to take up space or removed...
