Related
Seems that after the november update I cannot connect my pixel 2 xl to my 2017 honda crv. I've tried different cables, factory reset the head unit, delete AA, try older versions of AA, cleaned the usb port on the phone. I am going to put back the Sept update and see if that fixes things. I was noticing glitches on oct update too. Anyone else?
Going back to Sept fixed it. I was noticing glitches in oct.
equlizer said:
Going back to Sept fixed it. I was noticing glitches in oct.
Click to expand...
Click to collapse
Did AA over BT work before you switched back? Let us know what happens with the December update.
AA didnt work period! How do you get it working over bluetooth? I think the vehicle has to be compatible to do that too.
Figured I'd post this since it seems to have changed a few things.
Today I got an update notification and the size seemed a bit large (~900 MB). I kinda was hoping it would be a surprise Pie update, but alas it is not. Still 8.0.0 oreo, but there are a few new things I noticed.
Calling Plus is no more. Appears to be replaced with VoLTE capabilities. Phone tried registering on the network, but I got an error. Regular calling seems to be fine.
Always on Display is different now. Similar functionality, but fewer options.
pjsnyc said:
Today I got an update notification and the size seemed a bit large (~900 MB). I kinda was hoping it would be a surprise Pie update, but alas it is not.
Click to expand...
Click to collapse
I know you're probably joking, but PIE is not going to show up as some random update. It's going to Korea carrier variants first. Maybe Q1 2019. Then everyone else. PROBABLY Q2 2019.
We will have plenty of notice about Pie, when it starts happening.
Sent via open market LG US998 V30/V30+
In any case, functionality has changed a bit. Just a heads up.
After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.
jjairal said:
After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.
Click to expand...
Click to collapse
Sometimes updates create issues on a phone running stable and fine with current rom and we wonder why we updated?
I bought this phone a month ago (living in India) and I find that phone is running absolutely fine, with great battery life and no issues whatsoever with August security update.
Now -- may be I will update to new update (whenever released for India phones) only after couple of weeks after going through feedback from users who updated.
I have read that lg v30 is part of google enterprise recommended which need to be regularly updated every 90 days for atleast security patch. I am from india and i got last update at end of august but till i am posting this message i didn't got any update which shows avery pathetic promise breach. Which not good for brand like lg i didn't expect from lg???
Sabarixda said:
I have read that lg v30 is part of google enterprise recommended which need to be regularly updated every 90 days for atleast security patch. I am from india and i got last update at end of august but till i am posting this message i didn't got any update which shows avery pathetic promise breach. Which not good for brand like lg i didn't expect from lg???
Click to expand...
Click to collapse
Don't be concerned on not receiving update. From what I am reading on some other threads for V30+ -- believe me, you are saved from issues in new updates released in other parts of the world for our phone. Phone is running absolutely fine with last update. We should wait for an update which will not give us any performance issues.
jjairal said:
After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.
Click to expand...
Click to collapse
Strange, I havent had problems with LTE after update.
Oct security updates
plus the usual unknown fixes/bugs/features
Can't believe HK is one of the first region to get update this time...
ultima888 said:
Oct security updates
plus the usual unknown fixes/bugs/features
Can't believe HK is one of the first region to get update this time...
Click to expand...
Click to collapse
I have just updated and then I found that the wireless charging stopped working
kyho01 said:
I have just updated and then I found that the wireless charging stopped working
Click to expand...
Click to collapse
I don't have this problem after update.
Wireless charge is fine.
我從使用 Tapatalk 的 XQ-AT52 發送
ultima888 said:
Oct security updates
plus the usual unknown fixes/bugs/features
Can't believe HK is one of the first region to get update this time...
Click to expand...
Click to collapse
I havn't even got the previous one yet. Are you updating OTA or using Xperia Companion?
kyho01 said:
I have just updated and then I found that the wireless charging stopped working
Click to expand...
Click to collapse
Wireless charging is working fine for me as well. Be warn this phone stop wireless charging if your usb is plugged in for whatever reason, even if you are simply using a usb dac for music purpose...
kardstormer said:
I havn't even got the previous one yet. Are you updating OTA or using Xperia Companion?
Click to expand...
Click to collapse
Updated via OTA. Got the previous (.170) version not too long ago too, so was surprised today to see another update so quickly.
ultima888 said:
Wireless charging is working fine for me as well. Be warn this phone stop wireless charging if your usb is plugged in for whatever reason, even if you are simply using a usb dac for music purpose...
Updated via OTA. Got the previous (.170) version not too long ago too, so was surprised today to see another update so quickly.
Click to expand...
Click to collapse
Alright thank you. My phones doesn't have any issues but generally I feel the phone is half-finished so i'm hoping for updates that will improve that.
Hi, in Italy still no updates. I have the August security patch ? how is that possible ??
Im still with 3.132, not sure why i dont get the update.
Nordic/EU firmware
Skickat från min XQ-AT51 via Tapatalk
Mario.D said:
Im still with 3.132, not sure why i dont get the update.
Nordic/EU firmware
Skickat från min XQ-AT51 via Tapatalk
Click to expand...
Click to collapse
Same. Quite dissapointed in the speed of security updates. Thought with the Sony being relative close to stock it would get them more timely.
Already got it and installed yesterday on SEA Firmware. Looks like it's just a security updates (or at least very minor bug fixes)
This firmware had several network issue on Thai carrier before, despite using it in correct region. VoLTE didn't work and Carrier Aggriation is limited to only H+L 2CA. These problem are still exist in the current version.
ultima888 said:
Wireless charging is working fine for me as well. Be warn this phone stop wireless charging if your usb is plugged in for whatever reason, even if you are simply using a usb dac for music purpose...
Updated via OTA. Got the previous (.170) version not too long ago too, so was surprised today to see another update so quickly.
Click to expand...
Click to collapse
Suddenly the wireless charging works again today after I swapped the 64Gb SD with a new 128Gb SD. Seems it is quite not stable.
My battery life is terrible after this update. TERRIBLE
killuminati206 said:
My battery life is terrible after this update. TERRIBLE
Click to expand...
Click to collapse
How terrible it is? More elaboration on that? Thanks.
First update always make battery terrible give some time
I have problem with the vpn and wifi since the previous version.
Whenever I have vpn enabled and tried to connect to a public wifi with a captive portal (a page that requires the user to agree on terms), the captive portal will be blank.
The captive page can be displayed normally when vpn is disabled.
I have tried in settings, turning both "always on" and "block internet connections without vpn" on and off.
Is it a firmware or vpn app problem? The vpn app works fine with .132 version.
blegs said:
First update always make battery terrible give some time
Click to expand...
Click to collapse
Ive recieved previous updates on this phone before and battery life has remained stellar. Also my wireless charging is no longer working, which someone else mentioned about this update. UGhhh. Hope they fix. On previous update phone would come off charger at 8am and be good all the way through the day, with medium to heavy use. And now by 3pm my phone needs to be fully charged. This update is dog ****. Wish i knew how to revert back.
killuminati206 said:
My battery life is terrible after this update. TERRIBLE
Click to expand...
Click to collapse
Vanced user? Update all apps [emoji6]
Envoyé de mon XQ-AT51 en utilisant Tapatalk
Almost all have this firmware now except the European edition. Still at August update, this is getting weird
Brotuck said:
Almost all have this firmware now except the European edition. Still at August update, this is getting weird
Click to expand...
Click to collapse
My UK hand set got it last night
Sent from my XQ-AT51 using Tapatalk
US stuck on August also, typical
Must have heard me, I just got 170 in US after posting top sentence 34 minutes ago
Welp, it's about time they finally said it:
Pixel 6 December Update Situation Just Got Worse
Google confirms it has paused the December update for Pixel 6 lineup due to connectivity bug. When is a fix coming? Not until late January.
www.droid-life.com
And there you have what many had thought! Good old googleeeee
So for the few like myself that got it pushed to my phone on MetroPCS (TMobile), what does that mean? I haven't had any dropped calls but my speeds have been slower and battery has been worse than what I remember with November patch.
According to the post, if you aren’t experiencing issues after the update, no action is required and just rock out until the late January update. Unless you want to factory reset and revert back to the November update.
selayan said:
So for the few like myself that got it pushed to my phone on MetroPCS (TMobile), what does that mean? I haven't had any dropped calls but my speeds have been slower and battery has been worse than what I remember with November patch.
Click to expand...
Click to collapse
I doubt if it means anything. You can always flash the November image, although dirty flashing (not wiping), especially when "downgrading" can cause more issues and trouble than it's worth. Hopefully this Monday, January 3rd we'll get the regular monthly update, and if so, your current December version will be superseded anyway. Edit: I missed that the source Google article said fixes would come out in late January, so I'm now not expecting a new update until then or even the first Monday of February.
Im alright without the Dec. update, no issues with mine besides the AOD all of sudden does no respond. Found an an app that took care of that issue plus not notification indicator now
Figures, I already factory reset last week after the December update so I wouldn't want to flash a stock November image at this point. I have some other issues with the phone like the one user posted with lines across the screen on videos but have not been able to get in contact with support. Will try to after the holidays and hope they don't give me the run around.
I'd really like to know where the fault is. The modem or some other partition?
In November, I would drop calls in dead spots. In December I would just lose call audio and have to call that person back.
More fan fair:
Google paused the December Pixel 6 update, but is just admitting to it now
The Google Pixel 6 December 2021 update rolled out to a select few. Now, Google is finally admitting that update's problems.
www.androidauthority.com
Boo Google! What the heck is going on? Late January?
I guess I'll be using my 4 XL one more month then...
I guess Google now knows why Samsung doesn't use their own modems in their phones, especially in the US.
But hey.....look at all these cool animations they introduced in A12
It's a very capable modem but no other phone on the market has it. Samsung hasn't documented any differences from the international S20 or S21. Only thing it doesn't seem to support the moment is VoNR for voice over 5G.
But I've said this previously, Samsung rewrote the modem for December. The blame likely lies with them.
I have a really bad feeling about all of this.
So also on the Dec update and things seemed good until I noticed today that my Amazon apps (Music and Shopping) both appear to be crashing and complaining about either Chrome not being updated (when it IS), and/or no internet connectivity, when both 5G and/or WiFi are available and all other stuff works fine.
Not sure if this is related at all, but this only started today after I tried to install Amazon shopping, now Music and Shopping don't work right.
I had the same problem with Amazon apps. I was able to get them to work by disconnecting my VPN.
banshee28 said:
So also on the Dec update and things seemed good until I noticed today that my Amazon apps (Music and Shopping) both appear to be crashing and complaining about either Chrome not being updated (when it IS), and/or no internet connectivity, when both 5G and/or WiFi are available and all other stuff works fine.
Not sure if this is related at all, but this only started today after I tried to install Amazon shopping, now Music and Shopping don't work right.
Click to expand...
Click to collapse
Are you using ad blocking? Whitelist the following if so:
*amazon*
Click to expand...
Click to collapse
LLStarks said:
It's a very capable modem but no other phone on the market has it. Samsung hasn't documented any differences from the international S20 or S21. Only thing it doesn't seem to support the moment is VoNR for voice over 5G.
But I've said this previously, Samsung rewrote the modem for December. The blame likely lies with them.
Click to expand...
Click to collapse
Lol "capable" modem.. Ok buddy
opz187 said:
Lol "capable" modem.. Ok buddy
Click to expand...
Click to collapse
Capable as in it can combine 5G signals when most other phones can't or don't have it enabled.
I was worried earlier this year that it couldn't. I should've worried more about all these goodies and even basic call functionality being untested.
roirraW edor ehT said:
Are you using ad blocking? Whitelist the following if so:
Click to expand...
Click to collapse
Nice, thanks man! Worked perfectly.
Now I did temp disable AdAway earlier and that did not seem to fix it, maybe I did not fully restart the app then, but now its good.
Now on my previous LG V60 I used AdGuard for years and had no issues with Amazon apps, not sure why AdAway would be different?
LOL ... "If you aren’t experiencing issues after the update, no action is required and you’re apparently very fortunate." (Google: "If you are not experiencing mobile connectivity issues, no action is required.") ... not exactly a very solid (software) engineering analysis ...
Apparently I'm one of those "very fortunate" people ... upgraded manually and I have not had any issues at all since the upgrade (4G network in Belgium). On the contrary, since upgraded, phone has been working flawlessly for me.
Hopefully we'll get a bit better explanation than just "we found and fixed the problem".
Happy end of year festivities for all of you ... stay healthy and safe !
Well, there you have it. For all those people who said it was my fault for flashing the December build and corrupting my 6 Pro - almost to the point of no return (to be clear, I'm not saying this was the major factor in pulling the release - but it doesn't look good imo)
Google delists faulty December 2021 update for Pixel 6 & 6 Pro, preventing manual updates
Google has now removed the Pixel 6's faulty December 2021 update from its website, to prevent it from being manually installed.
9to5google.com
Luckily I did not manually install it.
By the way, nicely done gGoolge! You've got enough information already and don't need people as guinea pigs for now.
I hope the coming up January update is workable and doable, I can not expcet an outstanding update, Google.
Alekos said:
Well, there you have it. For all those people who said it was my fault for flashing the December build and corrupting my 6 Pro - almost to the point of no return:
Google delists faulty December 2021 update for Pixel 6 & 6 Pro, preventing manual updates
Google has now removed the Pixel 6's faulty December 2021 update from its website, to prevent it from being manually installed.
9to5google.com
Click to expand...
Click to collapse
I don't think they removed it because it was corrupting people's phones.
Most likely it was due to the many complaints of connection issues people were/are having, though I didn't experience any issues... I'm currently on ProtonAOSP just to test it out.
bouchigo said:
I don't think they removed it because it was corrupting people's phones.
Most likely it was due to the many complaints of connection issues people were/are having, though I didn't experience any issues... I'm currently on ProtonAOSP just to test it out.
Click to expand...
Click to collapse
yeah that's fine. I agree. I should edit my post. I think there's multiple issues with this build. lots of reports of people corrupting their phones on this build. none for October or November, many for December. Can't say exactly why that is - but I feel there's a lot wrong with the December Build (not just connectivity issues). This is pretty huge. For Google to pull a build? I've only heard that once in the past 8 years for Google to do that.
December build works perfectly for me lol
P6P said:
December build works perfectly for me lol
Click to expand...
Click to collapse
The ancient problem. Some people are affected, others are not.
Now imagine that Googles QA consists of 10 people and all those 10 people were people with "build works perfectly for me" - so they pushed it out to the public, and kaboom.
I guess Google can only improve this process, by widening the QA across the globe (they need to test firmwares in all countries of sale + more device variations, meaning some with Google Backups, some with Backup transfers from an Iphone, from a Samsung, from an old Google etc.) - I have the feeling that they only test their firmwares on brand new devices, and we can see in this forum how many issues come from backups). Since - apparently - testing it in the USA does not help much for European network problems.
Morgrain said:
The ancient problem. Some people are affected, others are not.
Now imagine that Googles QA consists of 10 people and all those 10 people were people with "build works perfectly for me" - so they pushed it out to the public, and kaboom.
I guess Google can only improve this process, by widening the QA across the globe (they need to test firmwares in all countries of sale + more device variations, meaning some with Google Backups, some with Backup transfers from an Iphone, from a Samsung, from an old Google etc.) - I have the feeling that they only test their firmwares on brand new devices, and we can see in this forum how many issues come from backups). Since - apparently - testing it in the USA does not help much for European network problems.
Click to expand...
Click to collapse
Yes sure you are right but it's kinda weird what they did there.
P6P said:
December build works perfectly for me lol
Click to expand...
Click to collapse
the thing is, to pull an update is kinda crazy. and the issue seems to mostly be in EMEA (and some parts of North America). this has to be directly related to not using Qualcomm. It sucks, but its true.
This isn't a small company we're talking about here. They need to do better. MUCH Better. Look, I've used pixels from the beginning, and will always, but they still need to do better.
Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...
Alekos said:
the thing is, to pull an update is kinda crazy. and the issue seems to mostly be in EMEA (and some parts of North America). this has to be directly related to not use Qualcomm. It sucks, but its true.
This isn't a small company we're talking about here. They need to do better. MUCH Better. Look, I've used pixels from the beginning, and will always, but they still need to do better.
Click to expand...
Click to collapse
Yeah and that's even more weird now because im using EMEA and also live in that region. Just crazy what they did there.
foobar66 said:
Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...
Click to expand...
Click to collapse
Oh no lol. We won't have anything to play with then haha
foobar66 said:
Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...
Click to expand...
Click to collapse
they pulled the update due to the connectivity issues. Google will never (and shouldn't ever) remove the manual upgrade process. It had nothing to do with that process anyhow. it was the build specifically that was the issue. It could have happened to any manufacturer. Google removing the ability to manually update has no bearing on this.
What would happen if users needed to roll back an update? Or they don't have internet? Or the ota update doesn't work? No way Jose
This is an extreme move. Anyone who's flashing the December build manually should be tech savvy enough to flash the November radio if they're having network issues. Everyone should have the ability to choose what build they're running - I, for one, couldn't deal with all the November bugs again.
If they wanted to limit novice users from flashing manually, they could have removed the ability to flash Dec build from the Android Flash Tool - all that pulling the build does is leave the people already on Dec build with no backup plan in case of bootloop, etc.
I still can't wrap my head around why they haven't released a minor OTA update & carrier services fix to resolve the widespread radio issues - they could have negated all of this with a quick fix in mid December to tide everyone over until January, but instead are making people wait over a month for the next build to fix a simple problem.
DanielF50 said:
This is an extreme move. Anyone who's flashing the December build manually should be tech savvy enough to flash the November radio if they're having network issues. Everyone should have the ability to choose what build they're running - I, for one, couldn't deal with all the November bugs again.
If they wanted to limit novice users from flashing manually, they could have removed the ability to flash Dec build from the Android Flash Tool - all that pulling the build does is leave the people already on Dec build with no backup plan in case of bootloop, etc.
I still can't wrap my head around why they haven't released a minor OTA update & carrier services fix to resolve the widespread radio issues - they could have negated all of this with a quick fix in mid December to tide everyone over until January, but instead are making people wait over a month for the next build to fix a simple problem.
Click to expand...
Click to collapse
They just needed to replace the Dec radio.img with Nov radio.img and that's all. Like you said... That could be the mid dec build then
P6P said:
They just needed to replace the Dec radio.img with Nov radio.img and that's all. Like you said... That could be the mid dec build then
Click to expand...
Click to collapse
but pulling the build - means there's much more to this. it must. On the december build, I could force a Corrupt message simply by turning off location access to the "ImsSetting" service in the Privacy menu. November build it's fine.
I suspect there is something more going on here
Alekos said:
but pulling the build - means there's much more to this. it must. On the december build, I could force a Corrupt message simply by turning off location access to the "ImsSetting" service in the Privacy menu. November build it's fine.
I suspect there is something more going on here
Click to expand...
Click to collapse
Oh ok didn't know that. I have just heard about the data connection problems.
P6P said:
Oh ok didn't know that. I have just heard about the data connection problems.
Click to expand...
Click to collapse
yeah I think there's more to it. obviously I can't prove it. but October/november there weren't any "corrupt" messages appearing. December? tons on reddit and here...
Alekos said:
yeah I think there's more to it. obviously I can't prove it. but October/november there weren't any "corrupt" messages appearing. December? tons on reddit and here...
Click to expand...
Click to collapse
Dunno. I had a few issues with October and November build but December is fine. No issues at all.
P6P said:
Dunno. I had a few issues with October and November build but December is fine. No issues at all.
Click to expand...
Click to collapse
yeah I didn't have issues either... October, November... then just flashed December's build and got the corrupt message. when I saved it, it was fine, but it was a close one. Almost couldn't get it back. nothing would work... bootloader, ota, factory reset etc etc.... finally flashing original build from October, did the trick.
but it's been great... no issues with signal, fingerprint, battery life....all good
Alekos said:
yeah I didn't have issues either... October, November... then just flashed December's build and got the corrupt message. when I saved it, it was fine, but it was a close one. Almost couldn't get it back. nothing would work... bootloader, ota, factory reset etc etc.... finally flashing original build from October, did the trick.
but it's been great... no issues with signal, fingerprint, battery life....all good
Click to expand...
Click to collapse
Wait you mean corrupt message while updating? Never had that.