Anyone in the US get the update today? I have seen quite a few in the UK receive the update yesterday.
I have seen reports of people from Germany, US and UK that have AND have not yet received the update. At this point it's probably a slow rollout, for whatever reasons.Anyone in the US get the update today? I have seen quite a few in the UK receive the update yesterday.
https://xdaforums.com/t/unlocking-t...rate-fingerprint-reader.4352027/post-85848409For those who are using the unlocked P6P (not the VZ version) AND are on the Verizon network, please share the version that OTA updated you to.
Google released the image for P6P and P6, as well as OTA for sideloading. Each have separate versions for Verizon. This has happened in past devics. I would like to know which flash to use for an unlocked devices on the Verizon network--the generic version of the flash or the VZ-specific version?
Thanks.
You are correct, Google just likes to release firmware updates that do nothing.
Still waiting for it. Standard device from Google in Germany.Anyone still not get the update? I have the unlocked version from Google on Verizon.
Same here.
Anyone still not get the update? I have the unlocked version from Google on Verizon.
I'm assuming the latter build number is strictly for Verizon variant, bootloader locked customers
I found an old expired sim from Singapore. Update immediately started. When I changed back to my German sim while the update was preparing, it disappeared again. Update completed with the Singapore sim. I don't know if the update offers any improvements for me though.I got impatient and had a dummy T-Mobile sim laying around so I powered off and switched out my Verizon sim. An update immediately pulled. It took about an hour and 20 mins or so downloading, installing, and optimizing apps. Powered off when done and switched back the Verizon sim. My updated build number is SD1A.210817.036.
From what I've read SD1A.210817.036 is the build number for every Google phone minus Verizon customers. Theirs would be SD1A.210817.036.A8. I'm assuming the latter build number is strictly for Verizon variant, bootloader locked customers.
Anyway, things seem to be fine and I haven't noticed any issues. Fingerprint sensor worked 99% of the time before and works the same now... along with everything else.
Anybody else with this problem? My 6 Pro gets soft bricked with the
Are you able to take the OTA with a fresh start / no restoring data and apps?Anybody else with this problem? My 6 Pro gets soft bricked with the
SD1A.210817.036.
It loses the signal (Tmobile) then restarts to recovery saying
“Cannot Load Android System. Your Data May Be Corrupt” It gives me the option to "Try again." or to "Factory data reset."
Device Completely stock
This is what I have done
1
Try Again (Same behavior)
2
Factory Reset (Multiple times), would let me finish the setup but as soon restores my data and apps happens all over again.
3
Sideload Rescue OTA (SD1A.210817.036.) same ****
4 now with heavy weapons
Unlocked bootloader, manually flashed factory images (Unlocked) the factory image it's an older version but seems to work perfectly (I'm able to set up and restore my data, but the phone automatically downloads the OTA update and the same thing all over.
5
Got a device replacement (Hella lucky they had my device in stock)
6
Different new Pixel 6 Pro Same behavior as soon the OTA hits and finishes to restore my apps.
7
Tried Manually flash, use the online google tool with different builds (tried the Tmobile stock)
Always the same problem.
There's any way to wipe/repartition only the System portion? I remember having something similar back in the days with an S2 and was able to fix it with a Reflashing of the PIT partition through Odin
Any suggestions?
My accubattery says that my P6 Pro is capable of delivering 9h54minutes of SoT (discharge rate of roughly 10%/1hour), not sure if you are trolling, if you have a rogue app, a broken phone or if the P30 Pro indeed only loses 5% battery every hour of SoT, which would be a monstrous achievement.updated in the uk but phone is getting warm during use and battery life is poor, well compared to Huawei p30 pro its actually shocking, about half at best as i'm used to multiday battery life
The UI isn't as user friendly as EMUI, why is it so bad compared to EMUI, thought getting a Pixel phone would be an improvement, how wrong was i.
how quick are the software updates for these phones hopefully improvements are on the way
I also still wait for the update (EU unlocked, still running on pre-release .015), I talked to a Google rep and first he claimed that if the phone doesn't get an update, it's up to date - after telling him "no, I know that newer firmware is already out" - he checked for a minute and then told me, that I should expect the rollout for all phones including mine in the next 3 days.Anyone still not get the update? I have the unlocked version from Google on Verizon.
not sure on the screen on time but i have done nothing different to my normal saturday, so drove to MTB ride phone 100% out on the bike taking a few photos, its no not even 12hrs later and im down to 25% which is poor compared to P30 pro, not had a phone this bad on battery since iphone 3, this is just my experience so far lets hope there is a software update, i have the same apps installed on both phones, maybe EMUI just manages battery/apps better and my previous windows and Huawei phones have raised my expectations of what is an acceptable standard for battery lifeMy accubattery says that my P6 Pro is capable of delivering 9h54minutes of SoT (discharge rate of roughly 10%/1hour), not sure if you are trolling, if you have a rogue app, a broken phone or if the P30 Pro indeed only loses 5% battery every hour of SoT, which would be a monstrous achievement.
What is known however, and not everyone is aware of that, is that Google phones are constantly calling home - meaning they offer 100% app functions - and because of that, "idle" battery life (like 1% lost every hour, depending on the amount of apps, more) is relatively bad. You can easily fix this with apps like Naptime or Servicely, even though those might only function in a limited way without root.
As a reference: https://dontkillmyapp.com/
--
Concerning the phone getting warm, I am still not able to replicate this (except shooting videofootage, which is normal for the phone to get warmer, even though I certainly wouldn't call it hot, it doesn't get uncomfortable, it's just noticeable that it gets warmer) - are you, by chance, active in 5G networks? There is no 5G connectivity near my home, so I never used that, I am 4G or Wifi only. Maybe this is the rootcause for those people here that talked about heat issues.
What might also cause a heat issue is a big ass case that might trap heat between the phone and the case - do you use a case? which one do you use? Maybe we can further narrow it down, if people with the same set of problems all use 5G and/or have similar cases.
Several reports of the actual Verizon .036.A1 OTA, starting with @stevek216 at post #126.
Checking for the software update
[Please check your device to see if you already have the latest software installed. Verify your Build number matches the official build by checking Settings -> About phone -> Build number. See section below]
After you complete the phone setup, the software update automatically downloads silently in the background. After the download completes, it will prompt you to reboot the phone. In case the software update is not seen, follow the instructions below:
Go to Settings -> System -> System update -> Check for update
Install the software update
Depending on your network connection speed and amount of apps involved, this will take about 25-50 minutes
Reboot the device after taking the update
Updating your apps
Many of the key apps have new features and improvements for Pixel 6. Please check to make sure that your apps are up to date by going to Play Store -> Your Account Icon -> Manage apps & device -> Update all.
Timing
Due to deployment timelines and staged rollouts, some updates may not be available until 10/28.
Software update Build number
After the software update, your device software version (Settings -> About phone -> Build number) will be be one of the following:
SD1A.210817.036
SD1A.210817.036.A8 (Verizon customers)
It will come if they build it. I setup and popped the sim in. Be patient. It takes an hour to download. Damn. It's still updating. Best phone I ever had. I don't understand these complainers
My accubattery says that my P6 Pro is capable of delivering 9h54minutes of SoT (discharge rate of roughly 10%/1hour), not sure if you are trolling, if you have a rogue app, a broken phone or if the P30 Pro indeed only loses 5% battery every hour of SoT, which would be a monstrous achievement.updated in the uk but phone is getting warm during use and battery life is poor, well compared to Huawei p30 pro its actually shocking, about half at best as i'm used to multiday battery life
The UI isn't as user friendly as EMUI, why is it so bad compared to EMUI, thought getting a Pixel phone would be an improvement, how wrong was i.
how quick are the software updates for these phones hopefully improvements are on the way
Just for the hell of it, I just tried to flash the regular global .036 over the vzw .036.A8 version and it failed citing the image was older than what I currently have now and downgrade isn't an option. Oh well, like I said, the toggle is still there and working for me. We'll see what Google does next month. I am still feeling these are mostly modem optimizations built in to the image for the specific carrier mentioned. If you look at previous builds for all the other phones, there are several that are carrier specific, especially when a new OS is released. Then eventually, as someone else mentioned, they merge them all together after a few months. Probably settings and coding that needs to be worked out to have the images compatible with all carriers.Locking/Unlocking Bootloader - Android Source
There are only 3 ways this property could be changed:
1. At ROM build time
2. Via recovery
3. Kernel root access
The last 2 would require an unlocked bootloader.
Even extremely low level methods such as JTAG most likely wouldn't work due to Android Verified Boot protecting data integrity; if you were to change the binary code on a physical storage device (chip) you would also have to change the cryptographic signature it's verified against.
USNF 2.2.0 was written to use Zygisk, so Magisk 23010 or newer is required.
You are correct, Google just likes to release firmware updates that do nothing.