- Feb 6, 2017
- 96,716
- 12,527
- 113
Each phone different hardwareCan someone smarter than me explain why they would do this? It seems very strange.
Each phone different hardwareCan someone smarter than me explain why they would do this? It seems very strange.
What part seems strange to you?Can someone smarter than me explain why they would do this? It seems very strange.
Each phone different hardware
What part seems strange to you?
Each get different size updateEvery iPhone has different hardware.
Would it? I don't see why. But that would be a good reason why the phone being referenced to should be in the post because an issue might be unique to that model of phone.That for instance, the gboard update, would be different on different pixels.
Would it? I don't see why. But that would be a good reason why the phone being referenced to should be in the post because an issue might be unique to that model of phone.
Like I wrote some pixels have different camera capabilities (multiple lenses for example) then others, or different processors.
The phone model helps in trouble shooting as well.
I haven't received the Gboard update on my Pixel 4a either. Not too worried about that particular one.For reference, I have a Pixel 4a.
It makes sense that camera capabilities might be different with different models due to specific hardware. Some capabilities but not all.
Why aren’t some people getting the gboard update though? There is no hardware difference for the keyboard, is there?
Some app updates like Gboard might not reach everyone in one time frame same as dark mode is google server side that doesn't hit everyone apps at once , but say pixel camera app update could vary for different modelsFor reference, I have a Pixel 4a.
It makes sense that camera capabilities might be different with different models due to specific hardware. Some capabilities but not all.
Why aren’t some people getting the gboard update though? There is no hardware difference for the keyboard, is there?
It will take anywhere between 45 minutes to over an hour. There are several posts above about how long it took. Just let it go on doing its thing. It does take a unusually long time.Noticed a small 738kb update for my Pixel 4XL this evening. It's SPB3. 210618.016. I proceeded to install it, but it hangs about one third through optimizing apps. I tried rebooting and resuming the install and it hangs again while optimizing apps. Any ideas how I can force it to finish the install? I've installed 3 Android 12 betas so far with no problem.
Can try setting>apps>system apps>tap software and scroll to storage clear it's data and force stop itNoticed a small 738kb update for my Pixel 4XL this evening. It's SPB3. 210618.016. I proceeded to install it, but it hangs about one third through optimizing apps. I tried rebooting and resuming the install and it hangs again while optimizing apps. Any ideas how I can force it to finish the install? I've installed 3 Android 12 betas so far with no problem.
It'll be interesting to see if that works.Can try setting>apps>system apps>tap and scroll to storage clear it's data and force stop it
Sometimes it can but I updated my post forgot software lolIt'll be interesting to see if that works.
Well now I'm forced to take a screenshot of that so to keep all that straight.Sometimes it can but I updated my post forgot software lol
It took an hour, but all is ok now. Thanks for your help and other responders.It will take anywhere between 45 minutes to over an hour. There are several posts above about how long it took. Just let it go on doing its thing. It does take a unusually long time.
So it sounds like "server side" isnt the best way to roll these things out. Is that correct?Some app updates like Gboard might not reach everyone in one time frame same as dark mode is google server side that doesn't hit everyone apps at once , but say pixel camera app update could vary for different models
So it sounds like "server side" isnt the best way to roll these things out. Is that correct?[/QUOTE
it is a good way. In some cases it's the only way to roll out updates that require server side functionality, when not all computiting done at the client (phone) level. Server side updates roll out slowly so the applicable servers don't get bogged down with every user receiving updates at once.
If it worked like it was intended it wouldn't be as bad , but from what I seen it's been slow on certain things , maybe they have better handle on it nowSo it sounds like "server side" isnt the best way to roll these things out. Is that correct?