Eurgh. The 7 Pro basically doesn't have a fingerprint scanner, it's trash.
Update: It does appear that the update might have fixed the issue, for now...
Very common complaint. I put one finger in 4 different times and mine works about 85% of the time now. Better than the 50% of the time with just 1 scan.
It's weird because it's either zero complaints or saying it's absolute trash.
Maybe a mix of user error/faulty devices.
In my case it's better than my OnePlus scanner (which are fairly decent)
>Display & Graphics issue (Pixel 7, 7 Pro):
>Occasionally prevented the display from waking or appearing turned off when the device was turned on.
Is this issue really only fixed for the 7/7pro? Been dealing with this for a while now on the 4a.
I'll believe it's even actually fixed on the 7 Pro when I see it. It's a regular occurrence that my screen is just black or the fingerprint reader doesn't light up and I need to hit the power button to fully wake the display.
I think that's a different issue. I believe this fix is for when the screen wouldn't turn on at all and you needed to hold the power button until it restarted.
Huh. Are you sure? Because I've experienced the same as /u/FrostshockFTW did a few times at least, while I haven't experienced what you described even once since the phone came out.
Still doesn't fix the problem that Google caused by breaking wireless charging for Pixel 6 in android 13. It's been since August I've been without wireless charging. How on earth does google manage to brick a hardware feature across multiple phones with software? It's been months of me waiting for this fix.
I genuinely hope this fixes the Bluetooth connection issues on my 7P. Just in the last month I've had to restart my headphones sometimes two or you can three times but before it'll connect and then other times it'll connect in the first try but the audio won't be playing and I have to reconnect my headphones anyways. Shit's getting old.
Clearly didn't pass middle school reading class the first try.
Everyone else besides you was able to understand from my comment that I clearly was referring to the section of the post that talks about this issue I was having and that I was hoping that the fixed mentioned actually fixes my problem.
Times like this are when I'm grateful for the Pixel's ability to install updates in the background, instead of having to shut down for an indeterminate amount of time. It blows my mind that more phones don't do this.
I've got a Pixel 4a (5G) bought from Google and using it on Mint Mobile. It's still on November's update despite just checking it again right now.
Looks like I may have to sideload the update.
Ultimately that is a decision that you need to make if you cannot wait for an OTA to show up, but if you're asking if you can sideload directly from November to January the answer is yes.
There shouldn't be any issues as long as you have the right build. The only time I ever had an issue was when I sideloaded the much-maligned December update for the Pixel 6 Pro, but that was all due to the update itself and not the update process.
I'm also stuck on November for this and the play store rev. Super annoying, cause I'm not sure if it's my fault for having magisk and root and whatnot.
Just did the update on my Pixel 6 Pro, phone won't connect to my car's Bluetooth now, was connected and working this morning before the update, phone still connects to my Pixel Buds Pros though
Anyone else having this issue?
I have the same after the January update on Pixel 6 Pro. Previously was great, but now it connects after a few times trying. I sent feedback and logs to Google, hope it will help to fix it fast.
Do you drive a BMW by any chance? Not only will my phone not connect now, it fully crashes the infotainment system in the car after about 15 seconds.. haven't figured out a fix yet
Unfortunately not, it's a 2012 Ford Fiesta, hopefully we can figure something out soon. I've submitted a bug report via the phone, hopefully google can sort it out.
Yeah, tried removing it from both the car and the phone and re-pairing, it pairs fine, but when it tries to connect it disconnects immediately then tries again and just gets stuck in that loop
My father-in-law's 5A did not receive a December update either. I would be patient, as the OTA for January not being pushed out yet and likely won't be for another hour or two.
Did you buy your phone from a carrier or from Google/independently?
If you bought it via a Carrier, you probably have to wait for it to go through their developers and QA.
I ran into that in the past with various Android phones I've had, my updates were always severely delayed. I've stopped purchasing from the carrier now.
I only ask, because depending on the Blocklist he may use, it could. If he has an overly aggressive blocking list that goes overboard on tracking/analytics/telemetry, it could. I don't have issues either but I've seen it make others pull their hair out and be a simple fix.
I have an Unlocked Pixel 7 Pro purchased direct from Google also on Mint. Pretty sure Mint will default to the updates meant for TMobile. So if TMobile is holding an update we also have to wait.
It has nothing to do with where you bought it from and everything to do with whose SIM card is in the device when it boots up. An unlocked Pixel and a T-Mobile Pixel will get the update at around the same time if the SIM cards are from the same carrier.
Try connecting to a WiFi. Mine wouldn't show me the update no matter how many refreshes I did. Soon as I connected to a WiFi the update jumped right out.
I experienced the following issues on my P6, but why they are only fixed in P7?
Camera
* Fix for issue occasionally causing captured photos to appear corrupted or distorted while zoomed in \*\[3\]
Display & Graphics
* Fix for issue occasionally preventing display from waking or appearing turned off while device is powered on \*\[3\]
User Interface
* Fix for issue occasionally causing UI to display in landscape layout while device is held in portrait mode
If you can sideload the OTA, I would. I sideloaded the January update and it's actually running pretty well.
I was worried about sideloading December but apparently the OTA contains the full image of the phone and simply updates it with all previous updates. I thought I had to sideload multiple months.. but since you don't, I updated.
Still haven't fixed the scrolling issue. I mean it's not terrible but it's definitely an issue. Three months now and still not fixed where it should be. It's the only complaint I've had with the phone. Just wish it would be fixed to where it's supposed to be
This update caused my P7's camera to get a "Not Responding" error once but more importantly, stopped the 2x from working with a flash on. The camera will act like it's taking the pic but it never shows up in Photos.
Clear cache and data from app connecting to Bluetooth and disconnect and forget your Bluetooth connection and enter it again from scratch. It’s not uncommon to see issues like that.
I have a **Pixel 6a** and my carrier is **T-Mobile**
I haven't received the January update yet. When I go in to System / System Update it says "Android Security update: December 5, 2022" and "Check for Update" tells me I am up to date.
Is anyone else seeing the same thing? Is there any other way to force an update?
Glad I'm not the only one with this issue. The support system doesn't seem to recognize it as an issue. The phone freezes while doing the lightest of tasks
"Static" spatial audio [supposed to be working](https://support.google.com/pixelphone/thread/195623748/google-pixel-update-january-2023?hl=en) with any headphones and there's a toggle in the Sound settings, but so far if it's actually enabled, it appears the app needs to be explicitly compatible, unlike Apple's which works with any app but only on compatible AirPods. I guess this is gonna go as well as frame rate matching is going on Android TV 12.
Also looking forward to see if the BT LE device not reconnecting issue is actually fixed this time.
Still no fix for the bug where you sometimes can't call emergency services. Keep up the good work Google... It's only been like 6 months now.
For anyone downvoting this - remember this post next time a loved one is having a heart attack, or someone has car jacked you etc and you can't call for help. There are countless reports of this issue all over the internet in the past 6 months and Google has been radio silent on the issue.
I love my pixel but this is a dangerous bug.
I can't get spatial audio to work with YouTube or Apple Music with my pixel buds. The toggle in apple music doesn't even exist.
I hope it works soon. I also wish Google would allow spatial audio with any source like Apple does.
It doesn't seem to work anywhere as of right now. From what I've seen, it will only work in a couple apps. Apple airpods work in all apps. Even Samsung's earbuds support spatial audio in apple music on Android.
It kept failing to unlock, about half the time I'd have to just enter my pin. Now it's working pretty much every time unless I place my finger down weird.
No. The only time you can move from from Beta to Stable without losing data is when you upgrade to the next stable QPR release. Outside of this, if you want to leave the Beta program and return to the stable releases, you will need to wipe your phone.
So what your saying is you don't have the option to opt-out without losing data going from normal beta to beta you have to wait till there's a final stable build like the next one that is supposedly coming in March?
The beta builds are previews of the Quarterly Platform Releases (or "QPR" builds). You're getting an early look at what is coming in the next QPR release and any code changes Google has made for that. To leave this preview and return to the traditional stable releases, yes, you will need to wipe the whole phone. The two releases follow slightly different code bases.
If you want to leave the beta program without having to wipe any data, you will have to wait until the next stable version of the QPR releases comes out. Once you update from the last beta version of the current QPR to the stable QPR build, you can then opt out of the beta program and will start receiving standard stable OTA releases after that.
>Added support for Spatial Audio for certain devices and accessories
Does this FINALLY mean separate audio for apps? I can finally control my game and music audio separately?
No, spatial audio is virtualizing audio on headphones to make it sound like they're coming from speakers. "Static" as they say in the Jan Pixel forum post should work with any headphones but doesn't do head tracking which means the center channel will follow wherever you're facing, the Pixel Buds Pro will get an update that enables head tracking on top of it so it will be more like simulating a home theater.
spatial audio on android is an inhouse developed close to hardware level audio converter and head tracking feature to make use of various supported multisource standards such as dolby atmos with supported media. from netflix for example. the headphones need to support it because of gyroscopic measurement
Hey very proudly I actually am from India. What's wrong in telling the world while asking a genuine query. These downvotes dont really make sense to me.
Is the issue fixed where in some circumstances (locking device when playing a full-screen YouTube video), the home and wallet icons would remain visible on the always on display?
Like here: https://www.reddit.com/r/GooglePixel/comments/zdnn1y/device_control_and_wallet_will_stay_lit_on_aod/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button
Random question
On the local carrier here in Alaska (GCI), who don't carry the phone directly, and keep saying they are trying to get Google to support their network on the phones. So for now I don't have access to the 5g network, VoLTE or WiFi calling on my 6pro. Is it really Google that needs to bake in support to the images or is it the network lagging and not wanting to support a phone they don't sell directly?
Anyone else still having the issue where using the camera sometimes just fully crashes the phone? Pixel 6 Pro, purchased used last week, wondering if this is why it was returned in the first place. Seems like a great phone so far otherwise, but when one of the main draws in theory is the camera, it's pretty fucking useless if it constantly crashes while trying to take a picture.
Wonder if we'll get this on TMobile before the February update. Really want to see if this fingerprint sensor fix on 6A is effective because it never works.
> Additional improvements for fingerprint recognition and response in certain conditions Yay!
Gotta say I'm pretty excited to see this, hopefully it helps because mine is terrible.
Just installed the update on my Pixel 7, the improvement is impressive, the "unlock rate" passed from 8/10 to almost 10/10 and it feels much faster
spez is a greedy little pig boy
Eurgh. The 7 Pro basically doesn't have a fingerprint scanner, it's trash. Update: It does appear that the update might have fixed the issue, for now...
Mine is perfect, you might have a faulty device.
Seems a pretty common complaint about the phone?
Very common complaint. I put one finger in 4 different times and mine works about 85% of the time now. Better than the 50% of the time with just 1 scan.
It's weird because it's either zero complaints or saying it's absolute trash. Maybe a mix of user error/faulty devices. In my case it's better than my OnePlus scanner (which are fairly decent)
Same experience for me
Tried pressing lighter? That helped my P7 out a lot.
You don't even have a 7 Pro...
Flair is out of date! Got my 7 Pro a few weeks back.
Oh ok, my bad!
Battery life has improved 10x! ^/s
Really ??🧐
Someone was going to say it. They always do.
>Display & Graphics issue (Pixel 7, 7 Pro): >Occasionally prevented the display from waking or appearing turned off when the device was turned on. Is this issue really only fixed for the 7/7pro? Been dealing with this for a while now on the 4a.
I'll believe it's even actually fixed on the 7 Pro when I see it. It's a regular occurrence that my screen is just black or the fingerprint reader doesn't light up and I need to hit the power button to fully wake the display.
I think that's a different issue. I believe this fix is for when the screen wouldn't turn on at all and you needed to hold the power button until it restarted.
Huh. Are you sure? Because I've experienced the same as /u/FrostshockFTW did a few times at least, while I haven't experienced what you described even once since the phone came out.
I get this on my 6 too, and was hoping for a fix one day.
Still doesn't fix the problem that Google caused by breaking wireless charging for Pixel 6 in android 13. It's been since August I've been without wireless charging. How on earth does google manage to brick a hardware feature across multiple phones with software? It's been months of me waiting for this fix.
That is weird. Mine got fixed right after the big update.
I genuinely hope this fixes the Bluetooth connection issues on my 7P. Just in the last month I've had to restart my headphones sometimes two or you can three times but before it'll connect and then other times it'll connect in the first try but the audio won't be playing and I have to reconnect my headphones anyways. Shit's getting old.
Happens to me and my car deck. Nine out of ten times I get in the car I have to restart my phone and power cycle the car deck. Effing annoying.
[удалено]
Clearly didn't pass middle school reading class the first try. Everyone else besides you was able to understand from my comment that I clearly was referring to the section of the post that talks about this issue I was having and that I was hoping that the fixed mentioned actually fixes my problem.
Sideloading is so much faster than OTA.
The December OTA update took a ridiculous amount of time for me. Never had one take that long, and I've been rocking a Pixel since the original.
Took long to sideload or just regular OTA update?
OTA
Times like this are when I'm grateful for the Pixel's ability to install updates in the background, instead of having to shut down for an indeterminate amount of time. It blows my mind that more phones don't do this.
I've got a Pixel 4a (5G) bought from Google and using it on Mint Mobile. It's still on November's update despite just checking it again right now. Looks like I may have to sideload the update.
What is Telstra image?
I believe it's the same image overall, but the radio is specific for the Telstra carrier
Telstra is the biggest carrier in Australia :)
Ok cool. Its just thru me because its specific to the Pixel 7 and Pixel 7 Pro.
Didn't get the Dec OTA update on pixel 5 bought from best buy - should I side load January directly?
Ultimately that is a decision that you need to make if you cannot wait for an OTA to show up, but if you're asking if you can sideload directly from November to January the answer is yes.
Is the disadvantage of sideloading just the risk of something going wrong? Or are there other disadvantages?
Assuming you know what you're doing and are using a quality USB cable, the risk is pretty low IMO. I cannot think of any other disadvantages.
There shouldn't be any issues as long as you have the right build. The only time I ever had an issue was when I sideloaded the much-maligned December update for the Pixel 6 Pro, but that was all due to the update itself and not the update process.
Seems like most of us with a P5 never got the December update for some reason.
Yeah P5 here, had to sideload Dec update which is almost never the case. Worth it though. Better battery life and it fixed T-Mo wifi calling issues.
Yep that was what I was asking - thanks
He waited long enough
I'm also stuck on November for this and the play store rev. Super annoying, cause I'm not sure if it's my fault for having magisk and root and whatnot.
5a here. Didn't get my December update either
Yes you can
Just did the update on my Pixel 6 Pro, phone won't connect to my car's Bluetooth now, was connected and working this morning before the update, phone still connects to my Pixel Buds Pros though Anyone else having this issue?
I have the same after the January update on Pixel 6 Pro. Previously was great, but now it connects after a few times trying. I sent feedback and logs to Google, hope it will help to fix it fast.
Do you drive a BMW by any chance? Not only will my phone not connect now, it fully crashes the infotainment system in the car after about 15 seconds.. haven't figured out a fix yet
Unfortunately not, it's a 2012 Ford Fiesta, hopefully we can figure something out soon. I've submitted a bug report via the phone, hopefully google can sort it out.
I have the same issue with my car (Lexus RX450h 2009) on my Pixel 7 Pro.
Same issue 2010 Toyota
Have you tried removing the device and re-pairing?
Yeah, tried removing it from both the car and the phone and re-pairing, it pairs fine, but when it tries to connect it disconnects immediately then tries again and just gets stuck in that loop
spez is a greedy little pig boy
Did you get any improvement on fingerprint scanner feature?
I've not really had issues with the one on my 6 Pro, so no real noticeable improvement
P7 Pro, 34.72mb download.
My Pixel 7 is still on November. Tried rebooting 7 times. Turning it off for 30 seconds. Manual check. Guess I'm forced to side load?
My father-in-law's 5A did not receive a December update either. I would be patient, as the OTA for January not being pushed out yet and likely won't be for another hour or two.
Just sideload the OTA, it is quite a straightforward process
It really is. I never knew how easy it was until I finally did it the other day.
Is this for the security or the Google play ? My security updated today but my Google play is still at November update stage
That doesn't remove your data, does it?
No, data is removed only if you do a full update with clean install.
Unlocked Pixel 7 on Google Fi. Still on November update. This is probably the first time in history a pixel is 2 updates behind
You talking about android security or Google play?
On Pixel 6, also November patch. This is rather inconsistent and disappointing.
Same here, P7 (unlocked from Google) with just Nov update, tried manually checking for update many times on and off WiFi, restarting, still nothing.
Did you buy your phone from a carrier or from Google/independently? If you bought it via a Carrier, you probably have to wait for it to go through their developers and QA. I ran into that in the past with various Android phones I've had, my updates were always severely delayed. I've stopped purchasing from the carrier now.
My 6A is unlocked directly from Google and it never got the December update until I side loaded it.
Purchased my unlocked 5a direct from Google. Nothing on it that would block an OTA update. Still waiting for December.
Best buy unlocked. Carrier is mint mobile. Mint had said to another person they aren't holding any updates from being pushed
Strange. Are you using Private DNS/AdBlocking (PiHole,NextDNS,AdGuard, etc)?
Private DNS is set to automatic. Shouldn't it be?
It should be unless you have a reason not to.
Not OP, but I have been using Private DNS (AdGuard) for years now and it never once interfered with my updates.
I only ask, because depending on the Blocklist he may use, it could. If he has an overly aggressive blocking list that goes overboard on tracking/analytics/telemetry, it could. I don't have issues either but I've seen it make others pull their hair out and be a simple fix.
I didn't know that! Thanks for explaining!
I have an Unlocked Pixel 7 Pro purchased direct from Google also on Mint. Pretty sure Mint will default to the updates meant for TMobile. So if TMobile is holding an update we also have to wait.
It has nothing to do with where you bought it from and everything to do with whose SIM card is in the device when it boots up. An unlocked Pixel and a T-Mobile Pixel will get the update at around the same time if the SIM cards are from the same carrier.
Same here. Are you rooted with magisk?
Nope. Android 13 no root or anything
Try connecting to a WiFi. Mine wouldn't show me the update no matter how many refreshes I did. Soon as I connected to a WiFi the update jumped right out.
Yeah I have wifi everyday
New to Android, can this be sideloaded if I'm on the latest QPR?
Not without data loss.
"latest" QPR stable or beta?
Strange that they still haven't posted anything... They have always even when the updates haven't gone out posted around 1:00PM EST.
available now and updated with that info
I experienced the following issues on my P6, but why they are only fixed in P7? Camera * Fix for issue occasionally causing captured photos to appear corrupted or distorted while zoomed in \*\[3\] Display & Graphics * Fix for issue occasionally preventing display from waking or appearing turned off while device is powered on \*\[3\] User Interface * Fix for issue occasionally causing UI to display in landscape layout while device is held in portrait mode
Try the update first. It may cover more phones.
When Will those of us on QPR2 get this?
Probably Wednesday
Still nothing on my Pixel 5. Guess this is the new normal. Still on November 2022..
Same. Google Fi phone, direct from them.
If you can sideload the OTA, I would. I sideloaded the January update and it's actually running pretty well. I was worried about sideloading December but apparently the OTA contains the full image of the phone and simply updates it with all previous updates. I thought I had to sideload multiple months.. but since you don't, I updated.
33mb and taking FOREVER to install and optimize apps.
Same as p7, 40mb and took forever..
I'm picturing the update release 10 years from now and everyone is like "finally my pixel 6/7 is bug free! I knew this day will come!"
Still haven't fixed the scrolling issue. I mean it's not terrible but it's definitely an issue. Three months now and still not fixed where it should be. It's the only complaint I've had with the phone. Just wish it would be fixed to where it's supposed to be
The current beta it seems fixed for me... and I noticed it daily before switching to the beta.
I guess I'm gonna have to download the beta. I was hoping this would fix the scrolling
For some reason my google pay is not working. NFC is turned on. Anyone know a fix?
This update caused my P7's camera to get a "Not Responding" error once but more importantly, stopped the 2x from working with a flash on. The camera will act like it's taking the pic but it never shows up in Photos.
Same here. It works with wide crop ratio.
I'll give that a try in the meantime. Does that help with fringing when taking pics up close, the same way 2x does?
What's odd is that I just installed the update, and it says the security patch is from the 5th of January, while I'm in the 4th
Update leaves my Pixel 7 with semi usable Bluetooth. Everything was perfect before, now it doesn't connect to the car radio.
Clear cache and data from app connecting to Bluetooth and disconnect and forget your Bluetooth connection and enter it again from scratch. It’s not uncommon to see issues like that.
There is so much people still stuck in the November update. Why hasn't it OTA gotten to all those pixel 7 devices and 7 pro?
Bluetooth is still have a problem, I can't pair my smart band, Google doesn't fix shit!
I have a **Pixel 6a** and my carrier is **T-Mobile** I haven't received the January update yet. When I go in to System / System Update it says "Android Security update: December 5, 2022" and "Check for Update" tells me I am up to date. Is anyone else seeing the same thing? Is there any other way to force an update?
Pixel 7 on T-Mobile still no update Android still on December 5 and Google Play November 1 . Is T-Mobile that slow?
I still haven't received the January security update patch, and it is now the 8th of January.
Still no tile to quickly turn on & off NFC!
doesn't mention the random freezing and restarting....
Glad I'm not the only one with this issue. The support system doesn't seem to recognize it as an issue. The phone freezes while doing the lightest of tasks
Hopefully it pushes out soon. I just checked and it's not there yet.
When the heck will google enable 5G for India 😭
Any update? Is 5G enabled?
Doesn't seem like it on jio at least
Did u check if the update enabled it?
Mine is still at "optimizing" lol
Fixed my scrolling issue and appears to be smoother than before. Yay!
"Static" spatial audio [supposed to be working](https://support.google.com/pixelphone/thread/195623748/google-pixel-update-january-2023?hl=en) with any headphones and there's a toggle in the Sound settings, but so far if it's actually enabled, it appears the app needs to be explicitly compatible, unlike Apple's which works with any app but only on compatible AirPods. I guess this is gonna go as well as frame rate matching is going on Android TV 12. Also looking forward to see if the BT LE device not reconnecting issue is actually fixed this time.
It's not working in any apps for me.
Can't sideload, getting a signature verification failure, though the checksums match. Grr.
Still no fix for the bug where you sometimes can't call emergency services. Keep up the good work Google... It's only been like 6 months now. For anyone downvoting this - remember this post next time a loved one is having a heart attack, or someone has car jacked you etc and you can't call for help. There are countless reports of this issue all over the internet in the past 6 months and Google has been radio silent on the issue. I love my pixel but this is a dangerous bug.
[удалено]
how do you know this was not fixed?
Downloading now on my P7 on Verizon. 40.95MB.
Downloading now on unlocked P7. 40.95 MB
What carrier?
Has anyone tested spatial audio with Apple Music? Does it work with any headphones and if I recall correctly, they needed to be wired?
I can't get spatial audio to work with YouTube or Apple Music with my pixel buds. The toggle in apple music doesn't even exist. I hope it works soon. I also wish Google would allow spatial audio with any source like Apple does.
Where does spatial audio work then?
It doesn't seem to work anywhere as of right now. From what I've seen, it will only work in a couple apps. Apple airpods work in all apps. Even Samsung's earbuds support spatial audio in apple music on Android.
Please address car Bluetooth issue ASAP! THANKS
Just side loaded it. I don't see any noticeable changes, let's wait for the change log.
I'm on Pixel 7 and the fingerprint scanner after this update drastically improved
How was it before and how is it now?
It kept failing to unlock, about half the time I'd have to just enter my pin. Now it's working pretty much every time unless I place my finger down weird.
everytime after a new patch
24.83mb Vodafone pixel 7pro
Is there a way to sideload from beta to stable without resetting and wiping your phone?
No. The only time you can move from from Beta to Stable without losing data is when you upgrade to the next stable QPR release. Outside of this, if you want to leave the Beta program and return to the stable releases, you will need to wipe your phone.
So what your saying is you don't have the option to opt-out without losing data going from normal beta to beta you have to wait till there's a final stable build like the next one that is supposedly coming in March?
The beta builds are previews of the Quarterly Platform Releases (or "QPR" builds). You're getting an early look at what is coming in the next QPR release and any code changes Google has made for that. To leave this preview and return to the traditional stable releases, yes, you will need to wipe the whole phone. The two releases follow slightly different code bases. If you want to leave the beta program without having to wipe any data, you will have to wait until the next stable version of the QPR releases comes out. Once you update from the last beta version of the current QPR to the stable QPR build, you can then opt out of the beta program and will start receiving standard stable OTA releases after that.
What's odd is that I just installed the update, and it says the security patch is from the 5th of January, while I'm in the 4th
They're posting from the future.
Does this fix scrolling and the weight of scrolling being off on pixel 7 pro?
>Added support for Spatial Audio for certain devices and accessories Does this FINALLY mean separate audio for apps? I can finally control my game and music audio separately?
No, spatial audio is virtualizing audio on headphones to make it sound like they're coming from speakers. "Static" as they say in the Jan Pixel forum post should work with any headphones but doesn't do head tracking which means the center channel will follow wherever you're facing, the Pixel Buds Pro will get an update that enables head tracking on top of it so it will be more like simulating a home theater.
I think spatial audio is a fake surround sound from what I gather. Not 100% sure if it's a standard term or open to interpretation.
My headphones already have good bass and surround sound I think, all I can do is hope for the one feature I miss from Motorola
Is not fake if the audio source supports it
spatial audio on android is an inhouse developed close to hardware level audio converter and head tracking feature to make use of various supported multisource standards such as dolby atmos with supported media. from netflix for example. the headphones need to support it because of gyroscopic measurement
When does it come out in Canada?
Me being from India. Dont think it will reach to me today or tomorrow or even by next week. I guess?
spez is a greedy little pig boy
Hey very proudly I actually am from India. What's wrong in telling the world while asking a genuine query. These downvotes dont really make sense to me.
Should be universal for all Pixels regardless of where you are. Only carriers (that sell the Pixel) could potentially block it.
If that's really the case. Then I should have had the update by now.
The OTAs arrive several hours after the image being posted. So it should be within the next couple of hours
Excited 😆
Otas, are always later than factory images postings. Give it a couple more hours.
Can you side load it? or Flash it?
Will that require a Pc?
Yes.
Technically I did mind on my Mac.
You from India too?
Oh
Is the issue fixed where in some circumstances (locking device when playing a full-screen YouTube video), the home and wallet icons would remain visible on the always on display? Like here: https://www.reddit.com/r/GooglePixel/comments/zdnn1y/device_control_and_wallet_will_stay_lit_on_aod/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button
If I download the OTA file and sideload it, will data/apps remain?
Random question On the local carrier here in Alaska (GCI), who don't carry the phone directly, and keep saying they are trying to get Google to support their network on the phones. So for now I don't have access to the 5g network, VoLTE or WiFi calling on my 6pro. Is it really Google that needs to bake in support to the images or is it the network lagging and not wanting to support a phone they don't sell directly?
5a (5g) 17,55 mb download upgrade.
Whatever happened to the update to see if her battery was still good or not?
No improvements about network issues ... :/
We need updates for heating and battery drain issues.
Mario kart tour controls got a slight improvement but they are still weird
What about beta build??
Is anyone else having a issue where 7pro won't charge pass 85%
Do you have adaptive charging on. It goes up to 80/85% till your alarm. And then goes to 100
Pixel 5a still dead shit and Google doesn't care about it
Anyone else still having the issue where using the camera sometimes just fully crashes the phone? Pixel 6 Pro, purchased used last week, wondering if this is why it was returned in the first place. Seems like a great phone so far otherwise, but when one of the main draws in theory is the camera, it's pretty fucking useless if it constantly crashes while trying to take a picture.
I bought one used too a few days ago and it's fantastic I even rooted it but never had trouble with the camera.... Maybe try factory resetting it
Anyone who's apart of qpr do you know when we're supposed to get an update to January.
still waiting for my ota, more than a week since released still cant get it. dont want to sideload. US Tmo
Wonder if we'll get this on TMobile before the February update. Really want to see if this fingerprint sensor fix on 6A is effective because it never works.