I just got the stand, and I noticed that when I get a notification, the display turns on and remains stuck at full brightness.
Wasn't this bug solved with some update?
The December update was supposed to be necessary for bug-free use with the Pixel Stand 2. Are you on November or December? They pulled the December update and you'd have to download it from the second thread in my signature below and manually update.
Note that I don't charge wirelessly so I can't report first hand experience.
https://redirect.viglink.com/?format=go&jsonp=vglnk_164190365622210&key=b8f771eed689587b82c4635131ce08d7&libId=kya31idk01010l04000MLp0cu9k7s&loc=https%3A%2F%2F9to5google.com%2F2021%2F12%2F30%2Fpixel-6-december-update-delay%2F&v=1&out=https%3A%2F%2Ftwitter.com%2FNexusBen&ref=https%3A%2F%2F9to5google.com%2F%3Fs%3DDecember%2Bupdate&title=Pixel%206%20December%20update%20has%20been%20delayed%20to%20January%20-%209to5Google&txt=%40NexusBen
Can you please have a delete button
boorog said:
Can you please have a delete button
Click to expand...
Click to collapse
There's always the Edit button. The closest thing to delete is the Report button, where you can ask a moderator to delete your post, although simply editing your post and replacing it with "delete" is fine too.
roirraW edor ehT said:
The December update was supposed to be necessary for bug-free use with the Pixel Stand 2. Are you on November or December? They pulled the December update and you'd have to download it from the second thread in my signature below and manually update.
Note that I don't charge wirelessly so I can't report first hand experience.
Click to expand...
Click to collapse
I'm on december update. To fully explain, even if I'm in flight mode, the "100% charged" message turns on the screen at full brightness.
gpvecchi said:
I'm on december update. To fully explain, even if I'm in flight mode, the "100% charged" message turns on the screen at full brightness.
Click to expand...
Click to collapse
Hopefully, that's another bug they'll squash with the January update later this month. That would be annoying!
Related
Solved: See post #7
I used to be able to Ok, Google and say "set countdown timer 2 minutes and 30 seconds" and it did it. Now when I do it, it brings up a screen to choose between either 2 minutes or 3 minutes. Did this start with the last update, or is there a setting I'm missing?
Edit: I contacted Moto 360 chat support and their response was to take it back to place of purchase!!
I was just about to complain about this, it was so handy to set count down timer without the need to touch the watch. Now it will just show the blue bullet menu and you have to confirm by touching the watch.... stupid....
Many complaints about it on google product forum
https://productforums.google.com/forum/#!category-topic/android-wear/9fcM_13j6so
lifeisfun said:
I was just about to complain about this, it was so handy to set count down timer without the need to touch the watch. Now it will just show the blue bullet menu and you have to confirm by touching the watch.... stupid....
Many complaints about it on google product forum
https://productforums.google.com/forum/#!category-topic/android-wear/9fcM_13j6so
Click to expand...
Click to collapse
Yes, I found that too. Hopefully it'll be back again.
Same issue with Lg g watch and google now on 5 different phones...
It seems like it broke on the last Wear update on the phone for me.
Jawbox said:
It seems like it broke on the last Wear update on the phone for me.
Click to expand...
Click to collapse
The issue has been posted in a few forums. I went ahead and did a review of Android Wear in the Playstore to report it. It probably won't hurt to have a lot of users report it via a review in the Playstore.
I think I found a fix for the countdown timer. On your phone, say OK Goggle, set countdown timer to 2 minutes and 45 seconds. (Any off the wall time will work). After it's done on your phone, try your Moto 360 now. It's working for me. If someone would confirm that it works, I'll rename to title of the thread to help others.
Problem is fixed now
They pushed update this morning.
lifeisfun said:
Problem is fixed now
They pushed update this morning.
Click to expand...
Click to collapse
Which update? I haven't gotten any update.
Edit: I just got the update, curious to know if the update fixes the timer issue. At the time I posted my fix, I had not gotten the update.
Idk if i got the update but i sure dont remember updating the Wear app. Although the fix you posted worked like a charm
April was Autism Awareness Month Sent from my SM-G900P using Tapatalk
Is anyone else noticing that wifi calling is getting turned off after a reboot? I'm on T-Mobile and ever since I updated to npf26j every time I reboot I have to go into the settings and turn wi-fi calling back on.
Given the fact that images have not been published to Google Dev site (yet), I wonder if npf26j was intended for the US market (or if it was actually a non-final version).
spaceman860 said:
Is anyone else noticing that wifi calling is getting turned off after a reboot? I'm on T-Mobile and ever since I updated to npf26j every time I reboot I have to go into the settings and turn wi-fi calling back on.
Click to expand...
Click to collapse
Yes I have noticed this after updating
I'm on Fi and don't have this problem with the setting changing.
tyea said:
I'm on Fi and don't have this problem with the setting changing.
Click to expand...
Click to collapse
Same here.
Mine turns off, T-Mobile user...
Sent from my Pixel XL
Yep. Mine turns off. It doesn't happen right away but a few seconds after I see the lockscreen it turns off. The double tap to see notifications is worth the minor inconvenience of having to turn on wifi calling after a reboot to me. Hopefully google fixes this once it is actually pushed out officially.
Glad to hear it's not just me lol. Not really a big deal since I hardly reboot anyways and having wake gestures is worth the minor issue. Hopefully when 7.1.1 comes out it will be fixed which I'm thinking will be with the Dec update.
There's a reason it's not an officially released build
I have T-Mobile and it stays on with no issues
Verizon here and mine stays on. I do notice intermittent issues with double tap to wake though. Sometimes it doesn't work, almost like the phone is in too deep of a sleep to wake.
JAYNO20 said:
Verizon here and mine stays on. I do notice intermittent issues with double tap to wake though. Sometimes it doesn't work, almost like the phone is in too deep of a sleep to wake.
Click to expand...
Click to collapse
My guess is this is related to the same bug where "Ok Google" doesn't work because it's sleeping too deeply after a period of time.
arcanexvi said:
My guess is this is related to the same bug where "Ok Google" doesn't work because it's sleeping too deeply after a period of time.
Click to expand...
Click to collapse
I think that is related to the app being "optimized" under battery. You can opt to not optimize the app and that should solve that issue...
xxfwmxx said:
There's a reason it's not an officially released build
Click to expand...
Click to collapse
Really, is that way there's a official OTA? Always gotta be that one useless poster.
spaceman860 said:
Really, is that way there's a official OTA? Always gotta be that one useless poster.
Click to expand...
Click to collapse
Wow talk about being that guy huh. Well not to be petty but show me where on Googles official page it shows the build? https://developers.google.com/android/ota
xxfwmxx said:
Wow talk about being that guy huh. Well not to be petty but show me where on Googles official page it shows the build? https://developers.google.com/android/ota
Click to expand...
Click to collapse
The ota link is official it came directly from Googles servers. Just because it's not on the page doesn't mean it's not official. Go be useless in another thread.
spaceman860 said:
The ota link is official it came directly from Googles servers. Just because it's not on the page doesn't mean it's not official. Go be useless in another thread.
Click to expand...
Click to collapse
Actually it does mean its not official. If it was they would have it on their public download page as well as they would be pushing it out to people. It's most likely a test build hence it issues people have had. Relax dude
xxfwmxx said:
Actually it does mean its not official. If it was they would have it on their public download page as well as they would be pushing it out to people. It's most likely a test build hence it issues people have had. Relax dude
Click to expand...
Click to collapse
Sorry but you're wrong. The ota hit my phone I didn't side load it. Anyways if you're not contributing just keep it moving.
It's official in the sense that it came from Google but it seems that it was an accidental release which is why it isn't available on the official OTA and factory image pages.
Sent from my Pixel XL using Tapatalk
7.1.1 update fixed the issue.
So I got this update today and of course the "learn more" link just pointed to the 4BQA2 update, which was just the first Nougat release, which I already had.
Anyone know anything about this one? It still says Android version 7.0, and the security patch level is 2/1/17. The kernel is 3.18.31 and is dated March 13th. The full build number is NRD90M.G930VVRU4BQA4
doncaruana said:
So I got this update today and of course the "learn more" link just pointed to the 4BQA2 update, which was just the first Nougat release, which I already had.
Anyone know anything about this one? It still says Android version 7.0, and the security patch level is 2/1/17. The kernel is 3.18.31 and is dated March 13th.
Click to expand...
Click to collapse
I just got it also, claims to improve wifi. My wife and I were just discussing that the GPS has been a bit laggy lately, maybe this will help that, too.
Yep just Wi-Fi fixes. Nothing to improve battery. Fail. still 7.0.0
Sent from my SM-G935V using Tapatalk
Checked SamMobile & Update.com & still no download link. Anyone know when or if they've released one yet?
Got it the other day as well
So far, no issues with the latest update. Still wish they'd fix the "switch keyboards" issue. Really annoying to go into the manage keyboards section and turn off all the other keyboards and leave the one on that you want to switch to. Otherwise, really happy with this. I got 20 hours on one charge and had about 27% left in battery. This was after playing games, reading email, reading news, surfing the web, texting and phone calls. I do have it on the mid-power saving mode, and I use the App Power Monitor that currently has about 89 apps flagged to be put to sleep when they're in the background. That really helps and is a built-in Greenify in Nougat. Really nice.
I wrote in another thread.
Can someone help? I just got the update to QA4,decided to go thru with the verizon wireless assistance programme via usb cable,now phone stuck on verizon screen bootloop. Any suggestions to save the day?
Update : safe mode doesnt boot up,either.
Can anyone confirm if this update fixes the Samsung calendar app from keeping the screen on when a reminder or calendar event pops up while the screen is off? This was introduced for me with the original nougat update.
cowman4000 said:
Can anyone confirm if this update fixes the Samsung calendar app from keeping the screen on when a reminder or calendar event pops up while the screen is off? This was introduced for me with the original nougat update.
Click to expand...
Click to collapse
Is the behavior you see?
Set screen timeout for 15 seconds. Set up a meeting in google calendar with starting in 7 minutes and reminder 5 minutes before meeting. Then wait for reminder on lock screen to pop up, don't touch anything and let screen timeout. See if screen will get activated again and go off after 2nd screen timeout.
If you get the same behavior, please report. I think there is something wrong with this as if you had a meeting reminder and the phone in you pocket, the phone battery will drain fast and phone gets hot of course.
Thanks
The behavior you described is similar except that the screen turns on for the initial reminder, then it times out and comes on again, times out and then turns on again and this is an endless cycle until I dismiss the reminder. I thought factory reset would fix it... But nope.
cowman4000 said:
The behavior you described is similar except that the screen turns on for the initial reminder, then it times out and comes on again, times out and then turns on again and this is an endless cycle until I dismiss the reminder. I thought factory reset would fix it... But nope.
Click to expand...
Click to collapse
That is exactly what I get. Is there a ticket opened with Samsung?
This seems to be the issue with Samsung pay https://forums.androidcentral.com/s...ar-notifications-keep-screen-post-nougat.html
What does BQC5 do? Has anybody recently received this update?
Tech180 said:
What does BQC5 do? Has anybody recently received this update?
Click to expand...
Click to collapse
Was it really that difficult to look just a few threads below this one to get your answer?
https://forum.xda-developers.com/verizon-galaxy-s7/how-to/security-bulletin-ota-update-s7-t3600060
Oh Woops! Thanks!
Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...
This is a known issue if you took the update by sideloading the OTA
ram4ufriends said:
Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...
Click to expand...
Click to collapse
Reboot your device once or twice and it should work normaly.
This has been an issue since 8.1. I've noticed it as well as on 8.0 my device woke up instantly.
Other users on reddit have seen the issue as well. Turning on ambient display to always on "fixes" it for me. Every user on this thread who says their device unlocks quickly has ambient display on. https://www.reddit.com/r/GooglePixe...el_2_xl_january_update_security_patch_jan_05/
Here's the official bug report on Google's tracker:
https://issuetracker.google.com/issues/69984153
I did factory reset, had no delay. As soon as I rooted. Had the delay.
ram4ufriends said:
Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...
Click to expand...
Click to collapse
One of the results of the Meltdown/Spectre malware "mitigation" security fixes is a slowdown. Because of the nature of the exploit block, lag is going to be experienced in most all operating systems.
DoctorB0NG said:
This has been an issue since 8.1. I've noticed it as well as on 8.0 my device woke up instantly.
Other users on reddit have seen the issue as well. Turning on ambient display to always on "fixes" it for me. Every user on this thread who says their device unlocks quickly has ambient display on. https://www.reddit.com/r/GooglePixe...el_2_xl_january_update_security_patch_jan_05/
Here's the official bug report on Google's tracker:
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
Yes, turning always on seems to be the fix as of now
wtherrell said:
One of the results of the Meltdown/Spectre malware "mitigation" security fixes is a slowdown. Because of the nature of the exploit block, lag is going to be experienced in most all operating systems.
Click to expand...
Click to collapse
My OG XL doesn't have this problem at all on the January 5th patch and meltdown only affects Intel x86 CPUs. Spectre affects quite a few ARM, MIPS and x86 chips but I refuse to believe that would cause a device to take 2-3x longer to unlock. Spectre fixes would incur a performance penalty on CPU demanding loads which waking a device up does not qualify.
Supposedly this issue has been fixed with the fix to be released at a future date. They said this in mid December, so doesn't look like the fix made it to the January security update. Hopefully the February one will have the fix
What's the latest versions the watch should be running.
Mine says Android 11 and security update is 1st July 22.
Is this correct or is there later versions?
It's correct same on mine , it's wear os 3.5 latest build so all good
Should we be getting a December update? I'm on Verizon and still waiting.
I got my update when I got the December update on my Pixel 7 two nights ago. (12/5/22) I am on Tmo in the US.
I just updated my 6 Pro. My watch "up to date" still shows Android V 11, July 1, 2022.
fred2546 said:
I just updated my 6 Pro. My watch "up to date" still shows Android V 11, July 1, 2022.
Click to expand...
Click to collapse
try connecting to Wifi and then going to update page and press the tick on the screen like 6 times. takes a while to get it to update
Nekromantik said:
try connecting to Wifi and then going to update page and press the tick on the screen like 6 times. takes a while to get it to update
Click to expand...
Click to collapse
I don't see a tick on my screen though.
GuyInDogSuit said:
I don't see a tick on my screen though.
Click to expand...
Click to collapse
No Tick here either.
Yer I didn't get the tick bit lol , but if you follow 9to5google
DoobyDroid said:
Yer I didn't get the tick bit lol , but if you follow 9to5google
Click to expand...
Click to collapse
That did it - it required being placed on the charger in my case. Here's a screenshot I captured. I had tapped that little icon before but probably not persistent enough.
Hello,
My watch started the update by itself (i didn't tap the icon as in the video), and it has freesed, now it doesn't start anymore.
The screen stay black, the green light at the back blink super fast when i move it, then stop after about 2sec.
Am-i the only one with this issue? Any idea how to fixe it?
Edit : i found a way, i needed to do a hard reboot :
How to fix a Pixel Watch with the black screen of death
This morning, I woke up to a bit of a troubling situation. Right as I was ready to leave the house, I went to my bedside table as I do every single day and I grabbed my earbuds, my phone, and my watch. As I situated my things in my pockets and onto my wrist,...
chromeunboxed.com