Related
You can punish them. Go to Google.com. Search for Verizon Galaxy Nexus. The very first result you'll see, in the paid search results, will be a link to Verizon.com.
Click on the link. Every time you click on the link Verizon has to pay Google for the "click through" ad.
Maybe it'll relieve some of your stress for waiting.
I had to lookup what miffed means.
Actually, Google is quite adept at recognizing duplicate clicks, and ignoring them.
Eh, 1 click per computer should go through
What I am miffed about...
http://source.android.com/source/building-devices.html
Just read the first two lines... LTE version is not supported for AOSP. Makes me wonder why...
I hope we still have the option to at least unlock the bootloader. I am going to wait it out for the info.
Tidbits said:
What I am miffed about...
http://source.android.com/source/building-devices.html
Just read the first two lines... LTE version is not supported for AOSP. Makes me wonder why...
I hope we still have the option to at least unlock the bootloader. I am going to wait it out for the info.
Click to expand...
Click to collapse
It's because the drivers for the LTE radios aren't available yet. Maybe they will be later.
http://code.google.com/android/nexus/drivers.html#maguroitl41d
Chirality said:
It's because the drivers for the LTE radios aren't available yet. Maybe they will be later.
http://code.google.com/android/nexus/drivers.html#maguroitl41d
Click to expand...
Click to collapse
i understand that, and I noticed that, BUT if I can't fastboot it then what was the point of me waiting... then having to wait longer because of a radio?
You can fastboot it, man. Drivers will be there when device is released.
Sent from my Nexus S using XDA App
matt2053 said:
You can fastboot it, man. Drivers will be there when device is released.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I'll still wait to see it. If it is like you are saying then *why* they disclaimer? The device isn't out yet and they could have said LTE version would be supported at a later date.
Sent from my DROID3 using Tapatalk
Tidbits said:
I'll still wait to see it. If it is like you are saying then *why* they disclaimer? The device isn't out yet and they could have said LTE version would be supported at a later date.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Nowhere in the page did they say the LTE version won't be supported.
The page is meant to be information for developers. It won't contain speculative statements.
it just passed through FCC
http://www.engadget.com/2011/11/15/...n-lte/?utm_source=engadget&utm_medium=twitter
Chirality said:
Nowhere in the page did they say the LTE version won't be supported.
The page is meant to be information for developers. It won't contain speculative statements.
Click to expand...
Click to collapse
On the page is SPECIFICALLY states the HSPA+ is OFFICIALLY supported. There is no mention of LTE like you said, but why even make a statement like that when BOTH devices are not even out.
This is why I am taking the sit and wait approach and see if it changes. I like to do things for myself, and I don't like using "hacks" to get what I want done. I purchased a Droid 3(old droid died) just to hold me off until I find the device or move carriers if need be.
I received an OTA software update with build number IMM76Q. Has anyone else received it?
Get us a logcat before installing please.
945kb...
Hmm.
Sent from my Galaxy Nexus using Tapatalk 2
Must be the gimping of the search bar
NeoMagus said:
Must be the gimping of the search bar
Click to expand...
Click to collapse
My exact thoughts!!
Yeah. 949 kb is tinyyyyy. I can't believe Verizon would be this quick about an update Google has been working on for a week and released a day or two ago! But no..... a somewhat major software revision has to take 2 months. I realize the fact that it is only a very, very small update, and it doesn't change any major software/radio stuff... but still. You know what would be cool? If verizon pushed out software updates (i.e 4.0.4, 4.1) clean at first, then follow up with a second update on the radios.
Lol nice "screenshot".
martonikaj said:
Lol nice "screenshot".
Click to expand...
Click to collapse
Next generation screenshot.
El Madhatter said:
I received an OTA software update with build number IMM76Q. Has anyone else received it?
Click to expand...
Click to collapse
Did you manage to get the file name for us yet?
If you've already installed it, the easiest way would be to look through the log files in /cache with a text viewer and look for a file name ending in .zip.
Thanks!
Wierd, even verizons support site doesn't have this update listed. http://support.verizonwireless.com/system_update/galaxynexus.html. Normally they list the update a few days before roll out on that site. Unless they really had to rush to get around the ban. Curious what's in this update, or if its real.
nbdysreal said:
Wierd, even verizons support site doesn't have this update listed. http://support.verizonwireless.com/system_update/galaxynexus.html. Normally they list the update a few days before roll out on that site. Unless they really had to rush to get around the ban. Curious what's in this update, or if its real.
Click to expand...
Click to collapse
As was mentioned, it is probably the disabling of the "local search" feature of the search bar.
martonikaj said:
Lol nice "screenshot".
Click to expand...
Click to collapse
Its the screen shot of all screen shots... Aero Shot ... comes in Jellybean lol
-Google
If anyone else gets the OTA, please post the filename here so I can update randomphantasmagoria.com. Thanks!
efrant said:
As was mentioned, it is probably the disabling of the "local search" feature of the search bar.
Click to expand...
Click to collapse
Yeah, i know thats what it probably is. Verizon just always puts out a pdf on the support sites of their phones no matter how minuscule the update is. Like one that turned off the initial 4g free tethering last year said something like "enables 4g tethering plans" or something like that. Oh you tricky VZ...
nbdysreal said:
Yeah, i know thats what it probably is. Verizon just always puts out a pdf on the support sites of their phones no matter how minuscule the update is. Like one that turned off the initial 4g free tethering last year said something like "enables 4g tethering plans" or something like that. Oh you tricky VZ...
Click to expand...
Click to collapse
Definitely very weird that VZW wouldn't have updated the support PDFs. They update those things religiously when there's an OTA.
I hope this IMM76Q update isn't another IMM30B where someone accidentally pushes it to a few devices, shuts it off, and it fades into the ether, leaving anyone who applied the update stranded.
anton2009 said:
Yeah. 949 kb is tinyyyyy. I can't believe Verizon would be this quick about an update Google has been working on for a week and released a day or two ago! But no..... a somewhat major software revision has to take 2 months. I realize the fact that it is only a very, very small update, and it doesn't change any major software/radio stuff... but still. You know what would be cool? If verizon pushed out software updates (i.e 4.0.4, 4.1) clean at first, then follow up with a second update on the radios.
Click to expand...
Click to collapse
Technically, the updates come from Google. Since this update has nothing to do with aspects that would be specific to carrier use they probably didn't involve Verizon in this one.
live4nyy said:
Technically, the updates come from Google. Since this update has nothing to do with aspects that would be specific to carrier use they probably didn't involve Verizon in this one.
Click to expand...
Click to collapse
As far as I'm aware, that's not an option. I believe VZW has to test and approve every single OTA that goes out to a phone on their network, regardless of how small or whether there is anything carrier-specific in it.
Apple is the lone exception to this rule. Verizon lets them do whatever the hell they want with the iPhone and iPad.
I spoke to a verizon tech rep this week---he said there was an update pending and suggested it was more about a radio fix. However, I'd take that with a grain of salt
oldblue910 said:
As far as I'm aware, that's not an option. I believe VZW has to test and approve every single OTA that goes out to a phone on their network, regardless of how small or whether there is anything carrier-specific in it.
Apple is the lone exception to this rule. Verizon lets them do whatever the hell they want with the iPhone and iPad.
Click to expand...
Click to collapse
That's very unfortunate then.
It's probably just an update regarding the whole patent situation
Apparently, Samsung still has a lot to learn with respect to providing their customers with a consistent message throughout the medias...
Yesterday afternoon on MobileSyrup.com, a Canadian based mobile news/reviews site...
Samsung Canada: Galaxy Note and Galaxy S III upgrade to Jelly Bean will arrive “before the holidays”
Now, this morning on TGDaily...
Galaxy S III Jelly Bean update may be in 2013
Ok, TGDaily provides no source to their information but still... this is kinda confusing and I would expect a company like Samsung to get their act together, don't you ?
I just ran into this Samsung announcement at BGR... There appears to be no specific timeline for the carriers.
http://www.bgr.com/2012/10/17/samsung-galaxy-s-iii-jelly-bean-upgrade-begin/
HiKsFiles said:
Apparently, Samsung still has a lot to learn with respect to providing their customers with a consistent message throughout the medias...
Yesterday afternoon on MobileSyrup.com, a Canadian based mobile news/reviews site...
Samsung Canada: Galaxy Note and Galaxy S III upgrade to Jelly Bean will arrive “before the holidays”
Now, this morning on TGDaily...
Galaxy S III Jelly Bean update may be in 2013
Ok, TGDaily provides no source to their information but still... this is kinda confusing and I would expect a company like Samsung to get their act together, don't you ?
Click to expand...
Click to collapse
Well both of those articles could be and probably are accurate. The galaxy s3 and notes on one or more of the Canadian networks will likely begin to receive jb during the holidays - mobile syrup is probably right on here.
And I'm sure tg daily is exactly right when it says some of the major US networks galaxy s3's will not get jb to 2013.
This information seems quite inline with what is going on - I'm not sure what you see as being contradictory or confusing.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
My experience with the Samsung Vibrant taught me a very valuable lesson - don't EVER expect timely OS updates when buying a Samsung device, unless that device is a Nexus.
kgbkny said:
My experience with the Samsung Vibrant taught me a very valuable lesson - don't EVER expect timely OS updates when buying a Samsung device, unless that device is a Nexus.
Click to expand...
Click to collapse
I have to agree and disagree at the same time. I have had multiple Samsung android phones, and multiple Motorola android phones. Samsung is already pushing out the JB update for their international S3, the only one that they have full control over the updates. Ours has to go through at least a month of carrier testing before att will push it out. The i747 updates even come off of ATTs server. All of the variants have their software pushed out by the carrier, which takes a lot longer. Samsung has had one of the fastest rollouts of JB on the international S3. Moto is much slower than Samsung, or at least have been in the past. This may change now that Google owns Moto. Even the Verizon Nexus JUST got JB, but the international has had it for a while. If you want timely updates, buy an international version of a phone.
dayv said:
Well both of those articles could be and probably are accurate. The galaxy s3 and notes on one or more of the Canadian networks will likely begin to receive jb during the holidays - mobile syrup is probably right on here.
And I'm sure tg daily is exactly right when it says some of the major US networks galaxy s3's will not get jb to 2013.
This information seems quite inline with what is going on - I'm not sure what you see as being contradictory or confusing.
Click to expand...
Click to collapse
Right, didn't see it this way.
It just seems odd that us canadians would be updated before you guys down south
I don't really think timing is Canadian or US dependent, but CARRIER dependent. The fact that the US & Canadian announcements above came out a day apart strongly suggests that Samsung will simultaneously provide the North American SG3 carriers with their updates and then release dates will be determined by the carriers.
Samsung must have already released the update to the carriers ... hence the announcements.
Considering there is a bell jelly bean leak i would say the carriers have had jelly bean for atleast a month now. I expect bell to release it first
Sent from my SGH-I747M using xda app-developers app
I would assume if you made it to xda you would stop blaming Samsung for carrier variants of phones getting updates. Whatever process carriers have to do to add there bloat has nothing to do with Samsung.
Blame AT&T bell T-Mobile etc.
Samsung sitting back saying we gave them that up date 3 months ago. Our guess is as good as theirs.
Sent from my SAMSUNG-SGH-I747 using xda premium
HiKsFiles said:
Samsung must have already released the update to the carriers ... hence the announcements.
Click to expand...
Click to collapse
This ^
js2021 said:
Considering there is a bell jelly bean leak i would say the carriers have had jelly bean for atleast a month now. I expect bell to release it first
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
This ^
If Samsung hasn't already given the update to all the carriers, they must of already given it to some of them. And I'm sure all the carriers will get something from Samsung (if not already) within the next two months. Then it will be up p to the carriers - some of which will take several months to get their respective customers.
dj_spore said:
I have to agree and disagree at the same time. I have had multiple Samsung android phones, and multiple Motorola android phones. Samsung is already pushing out the JB update for their international S3, the only one that they have full control over the updates. Ours has to go through at least a month of carrier testing before att will push it out. The i747 updates even come off of ATTs server. All of the variants have their software pushed out by the carrier, which takes a lot longer. Samsung has had one of the fastest rollouts of JB on the international S3. Moto is much slower than Samsung, or at least have been in the past. This may change now that Google owns Moto. Even the Verizon Nexus JUST got JB, but the international has had it for a while. If you want timely updates, buy an international version of a phone.
Click to expand...
Click to collapse
This is one of the reasons why I kept my Galaxy Nexus. As much as I like my GS3, software overlays and carrier interference typically spells extensive update delays.
Who has already updated phones to Jelly Bean? I don't really see a reason to complain. Or at least not to complain about a single device manufacturer. Samsung is generally pretty fast with updates compared to others. Either way they are dev friendly so that means you should have a custom update within a month of release to AOSP.
Do AT&T leaks show up on any AT&T servers? Or is the reason we don't have leaks because it is impossible to find them?
Sir_Brizz said:
Do AT&T leaks show up on any AT&T servers? Or is the reason we don't have leaks because it is impossible to find them?
Click to expand...
Click to collapse
The att leaks I have seen for previous Samsung phones were usually the result of someone who knew someone on the inside. I'm sure some of the time the leaks were intentionally put out by att for some free bug testing by the development community.
Design gears is one dev who at least in the past had a source - though I don't know how much dg spends on At&t phones or if he still has his connections. Also dg does not seem to spend much time on xda any more.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
intruda119 said:
I would assume if you made it to xda you would stop blaming Samsung for carrier variants of phones getting updates. Whatever process carriers have to do to add there bloat has nothing to do with Samsung.
Blame AT&T bell T-Mobile etc.
Samsung sitting back saying we gave them that up date 3 months ago. Our guess is as good as theirs.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
This is why I can't wait for next year when all manuf drop nexus devices. I can see this as people will probably stop buying the other phones manuf make and just get nexus devices. I'll probably cop a lg or htc nexus device myself. I'm tired of mother****ers playing with the updates and ****. I just want my vanilla android without the bull**** game playing
Sent from my SAMSUNG-SGH-I747 using xda premium
Just read 2 different stories on this. 1 says itll coming "in the coming months" (theverge.com) and the other says early next year.
http://www.theverge.com/2012/10/17/3516180/samsung-galaxy-s-III-jelly-bean-update-coming-months
http://www.androidauthority.com/u-s-galaxy-s3-jelly-bean-update-released-coming-months-123557/
Sent from my SAMSUNG-SGH-I727 using XDA
btm fdr said:
Just read 2 different stories on this. 1 says itll coming "in the coming months" (theverge.com) and the other says early next year.
http://www.theverge.com/2012/10/17/3516180/samsung-galaxy-s-III-jelly-bean-update-coming-months
http://www.androidauthority.com/u-s-galaxy-s3-jelly-bean-update-released-coming-months-123557/
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Seeing how its mid October both could be right.
kgbkny said:
My experience with the Samsung Vibrant taught me a very valuable lesson - don't EVER expect timely OS updates when buying a Samsung device, unless that device is a Nexus.
Click to expand...
Click to collapse
I don't see why people feel the need to say this about Samsung. This is fact for EVERY Android device other than the Nexus. LG/HTC/etc updates are no better, sometimes a slight ahead or slight behind, but they all take forever.
We all seem to be missing the point of updates. Its not the ROM itself, its the source code that we want.
http://www.tmonews.com/2014/02/andr...alaxy-s4-s4-note-3-and-other-samsung-devices/
Today, Samsung announced that it would be pushing out KitKat to a slew of its Android-powered smartphones. Although we’re not precisely sure on specific dates for T-Mobile devices, the 4.4.2 update will be rolling out from today.
Among the list of devices being supported are the Galaxy Note 3, Galaxy S 4 and S 3 as well as others. Full press release below:
DALLAS, February 18, 2014 – Samsung Telecommunications America (Samsung Mobile) announced today that a number of Samsung Galaxy® devices will receive the Android 4.4.2 (KitKat) software update, enriching the Galaxy experience.
The upgrade provides a number of innovative, easy-to-use features that enhance the user experience, including a more intuitive user interface, enhanced messaging capabilities and updated applications:
· Location Menu: An integrated location menu enables users to easily activate GPS, Wi-Fi and mobile networks, while simultaneously checking the battery usage of apps running location service capabilities.
· Enhanced Messaging: Enables users to choose between Messages or Hangouts as their preferred default messaging application, and select from a larger assortment of updated Emoji icons.
· Upgraded Google Mobile Service™ (GMS) apps: Users can automatically back up photos and video and can open, view, rename and share Google Docs and files.
Samsung Galaxy U.S. devices currently scheduled to receive the KitKat update include select carrier variants of the Galaxy Note® 3, Galaxy Note® II, Galaxy S® 4, Galaxy S® 4 mini™, Galaxy S® 4 Active™, Galaxy S® 4 zoom™, Galaxy S® III, Galaxy S® III mini™, Galaxy Mega®, Galaxy Light, Galaxy Note® 8.0, Galaxy Tab® 3, Galaxy Note® 10.1, Galaxy Note® 10.1 2014 Edition.
Availability varies by carrier and product, with updates beginning today and continuing throughout the coming months.
If you have one of the Galaxy devices mentioned in the announcement, be sure to let us know when/if the update lands. T-Mobile isn’t always speedy when it comes to giving the green light to software updates on Android. Let’s hope these start to land pretty snappish.
Nice. going to have to Odin back to stock then.
Still months away
TWEAKED 2.0 NOTE 3
Dattack said:
Nice. going to have to Odin back to stock then.
Click to expand...
Click to collapse
Don't update, the bootloader might be locked. It best to wait for a dev to get a hold of the firmware and make it into a flashable rom that doesn't include the bootloader.
marcoxx626 said:
Don't update, the bootloader might be locked. It best to wait for a dev to get a hold of the firmware and make it into a flashable rom that doesn't include the bootloader.
Click to expand...
Click to collapse
I am used to waiting to take updates being on VZW and what they did with breaking root with the Bionic and then the S4 fiasco. But why would Tmobile launch a phone with an unlocked bootloader only to lock it after an OTA update? It's one thing to patch an exploit, but to lock an unlocked bootloader when it was meant to launch unlocked I think would be stange. Again, I'm waiting anyway, but I think the phone will stay unlocked.
Not sure how excited I am for 4.4.2
No app ops. I can't believe google would intentionally remove a vital security feature. I guess we'll just have to add it back in
cun7 said:
Not sure how excited I am for 4.4.2
No app ops. I can't believe google would intentionally remove a vital security feature. I guess we'll just have to add it back in
Click to expand...
Click to collapse
I agree! In fact, that's the first thing I thought about when I heard about the news.
We do, however, still have xPrivacy, though. I've donated to the developer and hopefully we'll see continued development including, I hope, a more user-friendly system closer to the way App Ops works. (For the record, I'm not knocking xProvacy; rather I'm pointing out that it could be easier to manage for laymen like myself.)
Eric214 said:
I am used to waiting to take updates being on VZW and what they did with breaking root with the Bionic and then the S4 fiasco. But why would Tmobile launch a phone with an unlocked bootloader only to lock it after an OTA update? It's one thing to patch an exploit, but to lock an unlocked bootloader when it was meant to launch unlocked I think would be stange. Again, I'm waiting anyway, but I think the phone will stay unlocked.
Click to expand...
Click to collapse
i'm guessing you are right. But you have to remember, it's not TMO that's doing it. It's all part of Sammy Knox initiative to make the phones more secure. If you have an unlocked bootloader, there's no way to say that your product is secure. We've picked apart the last 3 builds /na6/na7/nb3 of kitkat from germany, and there's alot of pointless crap built into these roms that will have to be pulled out to , along with the regular developmental crap that sammy puts in there for "Future Updates" Like fingerprints scanner perms and instructions, radios that will never be used, and something pointing to a backup antennae even though the phone does not have one (that's for the note 10.1)
I think they are being lazy, , making one huge TW Rom and then modifying it for individual devices. If you look at the S4 release and the Note 3 release, they are identical builds minus screen size settings and the addition of spen support.
Any idea when the TMobile update will be available? Sprint customers are getting theirs from today.
Some people from g+ are claiming to get the Sprint updates yesterday. Wonder if someone from TMO got updated too.
There is a complete silence regarding Tmobile update. Even the dog slow at&t has a leaked version out.
Apparently us cellular is getting their update as well.
Here's the link if any one is curious.
http://phandroid.com/2014/02/20/us-cellular-note-3-kitkat/
I hope we're next
posted while using my note 3
I've have been with tmo from the beginning of this computer like smart phone generation, and I will say we are almost always the last to get an update. .. Our wifi calling and wifi alone had a bug for 6 months now no update when other carriers got the fix. .. Just saying. ...
Evertime there's an update these discussions happen. ... When when when. .. sit back relax and flash someone else's rom. ... lol
Sent from my SM-N900T using XDA Premium 4 mobile app
Call it eye-Kat. Make it look exactly like iOS and give Apple the finger
Sent from another galaxy
Check this out guys. Got it from comments on this article:
http://www.tmonews.com/2014/02/andr...alaxy-s4-s4-note-3-and-other-samsung-devices/
I'm on a KK custom ROM on my Note 3 so I'm not getting it. Maybe I need to flash back to stock. I'm in TX too btw.
djtheraven said:
I've have been with tmo from the beginning of this computer like smart phone generation, and I will say we are almost always the last to get an update. .. Our wifi calling and wifi alone had a bug for 6 months now no update when other carriers got the fix. .. Just saying. ...
Evertime there's an update these discussions happen. ... When when when. .. sit back relax and flash someone else's rom. ... lol
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IKR, the wifi bug is pissing me off!
Sent from my SM-N900T using XDA Premium 4 mobile app
marcoxx626 said:
Don't update, the bootloader might be locked. It best to wait for a dev to get a hold of the firmware and make it into a flashable rom that doesn't include the bootloader.
Click to expand...
Click to collapse
Apparently using Mobile Odin you can flash the update with rootkeeper and you keep Knox at 0x0 and get a rooted 4.4.2 (make sure you set it to reboot into download to flash the bootloader)
Details are in this thread:
http://forum.xda-developers.com/showthread.php?p=49502152
I wish T-Mobile would herry the heck up!!!!
dragonstalker said:
i'm guessing you are right. But you have to remember, it's not TMO that's doing it. It's all part of Sammy Knox initiative to make the phones more secure. If you have an unlocked bootloader, there's no way to say that your product is secure. We've picked apart the last 3 builds /na6/na7/nb3 of kitkat from germany, and there's alot of pointless crap built into these roms that will have to be pulled out to , along with the regular developmental crap that sammy puts in there for "Future Updates" Like fingerprints scanner perms and instructions, radios that will never be used, and something pointing to a backup antennae even though the phone does not have one (that's for the note 10.1)
I think they are being lazy, , making one huge TW Rom and then modifying it for individual devices. If you look at the S4 release and the Note 3 release, they are identical builds minus screen size settings and the addition of spen support.
Click to expand...
Click to collapse
Yeah i can see where you're coming from. but I still don't think Sammy will lock it down, but we'll see.
TMO is busy now with their "marketing campaign" to attract new customers.. They have no time to do software updates for existing customers
Come on peeps cut them some slack
daraj said:
TMO is busy now with their "marketing campaign" to attract new customers.. They have no time to do software updates for existing customers
Come on peeps cut them some slack
Click to expand...
Click to collapse
This is what I was afraid of when switching to TMO. Yeah I save money but at the cost of crappy CS service and very very slow to non-existant updates.
-Sent from my TMO Samsung Galaxy Note 3 using Tapatalk
Background:
At least two or three folks in this section have mentioned that if you have the factory unlocked Google Pixel 6 Pro, and you're using the phone on a carrier in the United States, that you shouldn't be using the December "SQ1D.211205.017 — US carriers" firmware, and that you should be using the "SQ1D.211205.016.A1 — “Global” (including CA, TW)" firmware.
This goes against logic for me and also turns what looks like a simple answer into a complicated one. As I try to keep things simple, and several other of us users believe you should use the firmware that's designated for the area you're using the phone in. i.e. If you're on a United States carrier, use the "SQ1D.211205.017 — US carriers" firmware.
In the end, any firmware should work on any phone in any area of the world, however, it may work better when using the designated one for your area as the firmware should contain optimizations for the radio.img to work with carriers in your part of the world.
I asked @NippleSauce if they could share the source of this information, and the following is what they shared. If anyone else has any more or different light to shed on this subject, please post here about it too.
NippleSauce said:
As for my information regarding the correct factory image to use, I don't have the links to where that information was discussed, however, it was stated by a Google employee on the Google forums and was also (I believe) discussed on Twitter from a Google rep. I may not be 100% correct on the other discussion happening on Twitter as I don't fully remember discovering everything related to the factory image confusion being that it was one of the first things that I had corrected after getting this phone. But, when I went to the correct factory image, a lot of the odd things that my phone would experience (such as an abnormally high usage temperature no matter what) were resolved. Perhaps the different P6 variants have a slightly different hardware design that isn't mentioned anywhere?
Click to expand...
Click to collapse
I am only looking for answers to the poll coming from those using the non-rooted factory unlocked Pixel 6 Pro on any United States carrier. I want to know which December OTA you received - for those few who actually received it.
I do see the info below at Google Pixel Update - December 2021, so I guess it's not completely unexpected.
Note: Users may either receive the global version or a regional specif
Click to expand...
Click to collapse
I'm not interested in what folks have manually flashed.
Only interested in poll results from those with:
Non-rooted factory unlocked Google Pixel 6 Pro
Running on a carrier in the United States
Actually received the December firmware update over the air - not manually flashed
You can find the firmware version you're on in Settings / About, at the very bottom "Build number".
Thank you for filling out the poll!
NippleSauce said:
As for my information regarding the correct factory image to use, I don't have the links to where that information was discussed, however, it was stated by a Google employee on the Google forums and was also (I believe) discussed on Twitter from a Google rep. I may not be 100% correct on the other discussion happening on Twitter as I don't fully remember discovering everything related to the factory image confusion being that it was one of the first things that I had corrected after getting this phone. But, when I went to the correct factory image, a lot of the odd things that my phone would experience (such as an abnormally high usage temperature no matter what) were resolved. Perhaps the different P6 variants have a slightly different hardware design that isn't mentioned anywhere?
Click to expand...
Click to collapse
Only three responses so far, all for "SQ1D.211205.017 — US carriers", not counting the five "None - for those who accidentally answered and realized they shouldn't".
That is the answer I expected, and that has been my experience with all my previous purchased Pixels unlocked from the store. I saw the comments that you referenced in your OP and did not believe them to be correct.
TonikJDK said:
That is the answer I expected, and that been my experience with all my previous purchased Pixels unlocked from the store. I saw the comments that you referenced in your OP and did not believe them to be correct.
Click to expand...
Click to collapse
Thanks! I'm always relieved to hear that something I always thought was simple can remain that way. I'm still hoping for some more responses, but it's only been one day.
just for reference, Im on AT&T.
had to manually start the OTA by mashing the check for update button, did not get a notification.
I am also of the opinion that you should (if you were to sideload) use the correct version for your circumstances. IE: the carrier version if you fit that criteria, as opposed to the global.
uicnren said:
just for reference, Im on AT&T.
had to manually start the OTA by mashing the check for update button, did not get a notification.
I am also of the opinion that you should (if you were to sideload) use the correct version for your circumstances. IE: the carrier version if you fit that criteria, as opposed to the global.
Click to expand...
Click to collapse
Thanks! At least mashing the button versus waiting for a notification shouldn't make a difference about which version you get.
It's interesting that one person who answered the poll on a US Carrier with the factory unlocked Pixel received the OTA to the Global version. I wonder what carrier they're on?
roirraW edor ehT said:
Thanks! At least mashing the button versus waiting for a notification shouldn't make a difference about which version you get.
It's interesting that one person who answered the poll on a US Carrier with the factory unlocked Pixel received the OTA to the Global version. I wonder what carrier they're on?
Click to expand...
Click to collapse
No, its the same mechanism to get the file. The method will make no difference. Was just pointing it out as many never got a notification and obviously never got the update manually as it was halted pretty quickly. Was just dumb luck for me as I happened to check and got it.
I'd be willing to bet they didnt get the international version (sideloaded it), or maybe they are roaming here and got the file for their home region. I'd bet it is some weird edge case and that its not truly an unlocked device actually registered to a US carrier.
I wonder if the global version would help US models.
I doubt it. I'm not sure if anyone has a complete dump of all the different firmwares.
I am one of the ones that have a P6 Pro on the Global version which was automatically pushed to my phone here in the US. I am on MetroPCS which is owned by T-Mobile. Not sure why this version was pushed but it showed up on December 14th.
I see 2 votes there now so there must be another person with the same version as me that also got it.
selayan said:
I am one of the ones that have a P6 Pro on the Global version which was automatically pushed to my phone here in the US. I am on MetroPCS which is owned by T-Mobile. Not sure why this version was pushed but it showed up on December 14th.
I see 2 votes there now so there must be another person with the same version as me that also got it.
Click to expand...
Click to collapse
Thank you! It's very interesting, indeed. I hope the other user who answered sees this and responds with their details as well.
I am curious now what version I will get for the January update. I would hope there would not be significant differences in battery life/performance (not that I notice any performance issues). But yea my battery has not been the best in general.
selayan said:
I am curious now what version I will get for the January update. I would hope there would not be significant differences in battery life/performance (not that I notice any performance issues). But yea my battery has not been the best in general.
Click to expand...
Click to collapse
I might just have to take another poll after the January update since I would expect more folks will receive it, so we get a better idea.
my cousins got verizon pixel 6 pro and said they received december update
Dragon Kumera said:
my cousins got verizon pixel 6 pro and said they received december update
Click to expand...
Click to collapse
I assume the .017 version. Thanks.
selayan said:
I am curious now what version I will get for the January update. I would hope there would not be significant differences in battery life/performance (not that I notice any performance issues). But yea my battery has not been the best in general.
Click to expand...
Click to collapse
I do see the info below at Google Pixel Update - December 2021, so I guess it's not completely unexpected.
Note: Users may either receive the global version or a regional specific version depending on their carrier
Click to expand...
Click to collapse
roirraW edor ehT said:
I assume the .017 version. Thanks.
Click to expand...
Click to collapse
They are not that tec savy I think but yes. I downloaded the full image and ota for my own 6 pro. I am on verizon