Double Tap to Wake - Broken in Jan Update? - Google Pixel XL Questions & Answers

Double Tap was working just fine on my Pixel XL. I applied the Jan OTA and re-rooted w/TWRP recovery without issue.
Double Tap to Wake is currently 100% non-functional. Lift to Wake is still working.
Is this an artifact of the update or some other factor? Phone seems to be 100% solid otherwise.
Any ideas/suggestions?

Mine works exactly the same as before since upgrading to U, which is to say I don't use it since it just gets to a swipe page and still needs a password/fingerprint. Much easier to just use a fingerprint. Now, double tap to sleep I'd use over pressing the lock button. What method did you do the OTA update?

sliding_billy said:
What method did you do the OTA update?
Click to expand...
Click to collapse
Thx for the reply. I used Flashall.bat (-w removed) to apply the update.

Strange since there was no application updating in this version (even Titanium didn't have any new updates or previously installed removals). Did you go from like version (O to U or Q to V)? I would just reflash considering how small the update is and how quick the TWRP/SU process is. FWIW, I have been using the OTA sideload through TWRP since I am going to end up with TWRP recovery (and not stock) anyways.

markp99 said:
Thx for the reply. I used Flashall.bat (-w removed) to apply the update.
Click to expand...
Click to collapse
Working fine here, too.

markp99 said:
Double Tap was working just fine on my Pixel XL. I applied the Jan OTA and re-rooted w/TWRP recovery without issue.
Double Tap to Wake is currently 100% non-functional. Lift to Wake is still working.
Is this an artifact of the update or some other factor? Phone seems to be 100% solid otherwise.
Any ideas/suggestions?
Click to expand...
Click to collapse
Do you have any kind of screen lock? Pattern, fingerprint, etc? If I use none, double tap or raise to wake have no effect, which makes sense.

I chatted with a Google help person (first time using that Pixel feature). Tried the usualt stuff:
1. Safe Mode
2. Toggled all the Motion settings
3. Toggled Security/Screen Lock settings
No luck.
Next step was a Factory Restore. I was not quite up for that process this morning, but may give it a go this evening. I rarely use that Dbl Tap to Wake feature and have no concerns if its an OS/Software-related issue. But if a Hardware/Sensor issue, I'd like to get it addressed sooner than later.

Re-flashing the update did not fix the issues, but a full Factory Refresh did.
A bit of a pain in the butt, but worth it to know not a hardware issue.

Related

PIN/Pattern required to enable fingerprint

Why is it when I set a fingerprint, I set a pattern for the mandatory backup security but when I try to unlock with fingerprint it asks for a pattern saying "Pattern required to enable fingerprint"?
As far as I know, as an extra security, a pattern/pin code is necessary when the phone is restarted/ switched on, once you chose to use the fingerprint scanner.
Howling Wolf said:
As far as I know, as an extra security, a pattern/pin code is necessary when the phone is restarted/ switched on, once you chose to use the fingerprint scanner.
Click to expand...
Click to collapse
It's every time I lock it
Sent from my HTC 10 using Tapatalk
Finally figured it out.
It happens when screen is locked by a 3rd party app, in my case I use nova double tap to lock screen.
Was wondering why (and forgot to mention) it seemed random.
Edit: for Nova users looking for a workaround, if you enable screen off by root access method it will use a secure lock and enable the fingerprint to unlock.
Heisenberg420 said:
Finally figured it out.
It happens when screen is locked by a 3rd party app, in my case I use nova double tap to lock screen.
Was wondering why (and forgot to mention) it seemed random.
Edit: for Nova users looking for a workaround, if you enable screen off by root access method it will use a secure lock and enable the fingerprint to unlock.
Click to expand...
Click to collapse
yeah a lot of screenapp does ask.... if you are on elementalx you could use button mapper which gives you the same functionality of double to sleep and more doesn't ask for patter/pin everytime you unlock
This started to happen to me after a bug crashed the phone and had to force restart it holding volume down + power. I only have the default launcher so I guess it's factory reset time for me
Heisenberg420 said:
Why is it when I set a fingerprint, I set a pattern for the mandatory backup security but when I try to unlock with fingerprint it asks for a pattern saying "Pattern required to enable fingerprint"?
Click to expand...
Click to collapse
For what it's worth, I had the same issue (until I found this thread) and it was caused by Action Laucher 3. The launcher was set as a Device Administrator and was granted permission to "Power screen off". Once I removed that permission my troubles were over.
Seems to me that it makes sense once you have a fingerprint setup, to require a pin as well. Why? Because what if the fingerprint reader stops working? You won't be able to login?!?!
Not sure until the poster above mentions a pattern is required. Normally it is a pin if you want. Then the PIN required upon restart option as well that is there.
Of course, if you are rooted, you can delete the system files that control/store that...but if not rooted with TWRP, you would have to try a master reset I would assume?!?!
IDK...guess I never thought of testing that out...haha
Guys, i hope it's ok if i conquer this thread for my question but i got serious issues here.
Got my 10 back from repair today and restored my backup.
But dumb me it seems as if i set a password/patern whatever and i can't remember it.
So after the first restart i can't unlock my phone cause it's asking for the code (and won't let unlock only with fingerprint) and i can't remember.
All combination that i would have used are wrong and now i got a working phone back again (after almost 2 month of repairing) and can't unlock it.
Is there any way of bypassing/ignoring the restart password or is it possible to only unlock it again with the fingerprint that is stored?
As i don't know what i should do if i don't get my phone unlocked
bmwbasti said:
Guys, i hope it's ok if i conquer this thread for my question but i got serious issues here.
Got my 10 back from repair today and restored my backup.
But dumb me it seems as if i set a password/patern whatever and i can't remember it.
So after the first restart i can't unlock my phone cause it's asking for the code (and won't let unlock only with fingerprint) and i can't remember.
All combination that i would have used are wrong and now i got a working phone back again (after almost 2 month of repairing) and can't unlock it.
Is there any way of bypassing/ignoring the restart password or is it possible to only unlock it again with the fingerprint that is stored?
As i don't know what i should do if i don't get my phone unlocked
Click to expand...
Click to collapse
Try a factory reset via Android Device Manager.
I don't know what Android Device Manager is but I could do the reset in TWRP too. It's about not losing all of my data or a possibility to get that device unlocked without the code. It would be no problem as my fingerprint is stored. Damn, I could just hit my head against a wall or alternatively just cry like a baby. I never forgot a password or code in my whole life and by now it happens
bmwbasti said:
I don't know what Android Device Manager is but I could do the reset in TWRP too. It's about not losing all of my data or a possibility to get that device unlocked without the code. It would be no problem as my fingerprint is stored. Damn, I could just hit my head against a wall or alternatively just cry like a baby. I never forgot a password or code in my whole life and by now it happens
Click to expand...
Click to collapse
Log in here https://www.google.com/android/devicemanager
Using the account your phone is used with.
Thx, but there I only have the options of letting the phone ring, lock it down or wiping it. As stated above I could do that easily in recovery, too.
I'm looking for a way of not having to wipe the phone (if there is one....)
bmwbasti said:
Thx, but there I only have the options of letting the phone ring, lock it down or wiping it. As stated above I could do that easily in recovery, too.
I'm looking for a way of not having to wipe the phone (if there is one....)
Click to expand...
Click to collapse
To be honest, I don't think so. There were loopholes before, but they have been closed. :/
So doing a factory reset and restoring /data is the only way of getting back control of my phone again (without losing too much data)?
I think i will get rid of locking my phone with fingerprint again as there seems not ot be a failsafe mechanic for forgetting a (backup) mechanic
OK, so it seems that I have to throw that piece of aluminum against the wall. The code seems to interact with /data, because after restoring only /data I have to put in the forgotten password again.
bmwbasti said:
OK, so it seems that I have to throw that piece of aluminum against the wall. The code seems to interact with /data, because after restoring only /data I have to put in the forgotten password again.
Click to expand...
Click to collapse
I really suggest starting from zero, when you get everything set, then set a password.
Thanks for your advice, but it's not about starting from zero. I've already done this twice today
It's about at least being able to get (some of) the data of /data

G930A_QE1_Stock_Deodexed_Rooted_ROM

This is my first ever ROM to post up. I just recently started building them. This is a stock deodexed Nougat ROM that is pre rooted. It is 100% AT&T Nougat with just a few fixes. I have left all Samsung and AT&T bloat for those that want all the bloat but like to be rooted and deodexed.
Follow the steps below for installation:
Step 1: You must already be on Nougat firmware. There are various threads on how to do this but if you can not figure it out just ask and i will try to assist you the best i can.
Step 2: Once on Nougat, root your device. Follow this guide https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Step 3: Once Rooted, install Flash fire from playstore.
Step 4: Open Flashfire and grant SuperSU access, once you are at the main menu, press the + and select Flash ZIP or OTA, go to the place you stored the ROM and selecet it. On the next screen MAKE SURE "Mount /system read/write" is selected and click the check mark in the upper right hand corner.
Step 5: Click the + sign again and select "Wipe", leave the defaulted boxes checked (System data, 3rd party apps, and Dalvik cache) and click the check mark in the upper right corner again. ( optional, you can select internal storage but you don't have to).
Step 6: VERY VERY IMPORTANT, select and hold down on Wipe and move it above "Flash ZIP or OTA"
Step 7: Make sure EverRoot is disabled and Reboot is set to normal.
Step 8: Click the lightning bolt and then yes on the next prompt, and let FF do it's thing.
*****Be patient, it will take up to 15 min to boot but most times it is quicker than that.*****
* Fixes i added
Fingerprint fix after root. Thanks to @qwewqa
Replaced IMSService.apk to remove hurricane icon.
CPU Fixes. Thanks to @stang5litre
Issues:
Phone forgetting Bluetooth devices after reboot, I am trying to find a fix for it and will update when i do.
Thanks @stang5litre for countless hours and days of walking me through so many steps from setting up my kitchen to fixing my phone via TV and ADB.
Thanks @SuperR. for the kitchen and all the continued support
Thanks @Chainfire for Flashfire and SuperSU
Download link: https://www.dropbox.com/s/17w8ut192jwixnw/G930AUCS4BQE1.zip?dl=0
Where did you get the ATT stock firmware?
Edit: nevermind I thought you had the latest firmware sorry. Good luck on your first rom
jrkruse said:
Where did you get the ATT stock firmware?
Edit: nevermind I thought you had the latest firmware sorry. Good luck on your first rom
Click to expand...
Click to collapse
Thanks bud. I've been looking for the latest but can't find it. I tried to pull it from my phone using superR kitchen but couldn't deodex it correctly. So inn still working on it. Lol
Congrats bud!!!
Cool. Does adoptable storage work with this ROM?
yuejon said:
Cool. Does adoptable storage work with this ROM?
Click to expand...
Click to collapse
This is 100% stock rooted, deodex, if it didn't work on stock unrooted, chances are that it don't work on this one either.
Hello, I've flashed the rom and loving it so far, it is buttery smooth and seems to have the same battery drain as in stock, but two problems... Every reboot or when I just turn off the wifi, it forgets the password. I've tried build prop editor and set ro.securestorage.suppprt to false, but no success. Another problem, Blutooth won't turn on. It used to before I changed the build prop, but now, it just doesn't turn on. I'm not sure if it is a problem with nougat root or your rom itself, I would love some answers. Otherwise the rom is great and I hope you continue to update it as there isn't a lot of development in AT&T.
OfferedBison said:
Hello, I've flashed the rom and loving it so far, it is buttery smooth and seems to have the same battery drain as in stock, but two problems... Every reboot or when I just turn off the wifi, it forgets the password. I've tried build prop editor and set ro.securestorage.suppprt to false, but no success. Another problem, Blutooth won't turn on. It used to before I changed the build prop, but now, it just doesn't turn on. I'm not sure if it is a problem with nougat root or your rom itself, I would love some answers. Otherwise the rom is great and I hope you continue to update it as there isn't a lot of development in AT&T.
Click to expand...
Click to collapse
Thank you for your feedback. I have experienced the Bluetooth issue on another more custom rom that I'm building, i haven't pin pointed it yet but am still working on it. I was originally thinking it had something to do with something that i removed from the rom (bloat) because when i run this rom with all the bloat i didn't have the issue. I will switch back to this rom and run it for a few days and see if the issue pops back up. As for the WiFi password, i have no problem with that and i have mine set to "true". I'll look into it though and get back with you.
For the battery drain, install kernel auditor, settings menu in top left corner, go to cpu, and set the governor to "on Demand" that will help a little bit.
dirtydodge said:
Thank you for your feedback. I have experienced the Bluetooth issue on another more custom rom that I'm building, i haven't pin pointed it yet but am still working on it. I was originally thinking it had something to do with something that i removed from the rom (bloat) because when i run this rom with all the bloat i didn't have the issue. I will switch back to this rom and run it for a few days and see if the issue pops back up. As for the WiFi password, i have no problem with that and i have mine set to "true". I'll look into it though and get back with you.
For the battery drain, install kernel auditor, settings menu in top left corner, go to cpu, and set the governor to "on Demand" that will help a little bit.
Click to expand...
Click to collapse
Thank you. The Bluetooth problem was fixed when I reverted the changes I made in build prop, and for the wifi problem I think it was something I froze in titanium backup, since I froze some bloat etc.
OfferedBison said:
Thank you. The Bluetooth problem was fixed when I reverted the changes I made in build prop, and for the wifi problem I think it was something I froze in titanium backup, since I froze some bloat etc.
Click to expand...
Click to collapse
The changes you made in build.prob? You mean by setting the secure.storage to false? I do know that on the custom Rom I'm building, i had it set to false and i was having the blue tooth issue, for the WiFi issue, it could be something you froze, can you SS your frozen list.
dirtydodge said:
The changes you made in build.prob? You mean by setting the secure.storage to false? I do know that on the custom Rom I'm building, i had it set to false and i was having the blue tooth issue, for the WiFi issue, it could be something you froze, can you SS your frozen list.
Click to expand...
Click to collapse
Here,
OfferedBison said:
Here,
Click to expand...
Click to collapse
Thanks, the only two things that I'm not sure what it is, is UPSM_N and com.android.Samsung. M. I'm not saying that could be causing it but I'll habe to research what those two things are. Thank you.
dirtydodge said:
Thanks, the only two things that I'm not sure what it is, is UPSM_N and com.android.Samsung. M. I'm not saying that could be causing it but I'll habe to research what those two things are. Thank you.
Click to expand...
Click to collapse
I defrosted android.samsung, but cannot defrost upsm.n, weird. This doesn't seem to be the problem as it still persists.
OfferedBison said:
I defrosted android.samsung, but cannot defrost upsm.n, weird. This doesn't seem to be the problem as it still persists.
Click to expand...
Click to collapse
So your still having the WiFi problem not remembering password after reboot? My ro.secure is set to true and I'm not having the issue.
dirtydodge said:
So your still having the WiFi problem not remembering password after reboot? My ro.secure is set to true and I'm not having the issue.
Click to expand...
Click to collapse
Unfortunately, yes. Maybe something went wrong when I flashed the rom... I'll try reflashing the rom later , when I have time.
OfferedBison said:
Unfortunately, yes. Maybe something went wrong when I flashed the rom... I'll try reflashing the rom later , when I have time.
Click to expand...
Click to collapse
ok. Yea i would try that. I can't duplicate the issue on my end. Leave the ro.secure storage set to true and see if that fixed it. That's what mine is set at and I'm not having any problems with Bluetooth or passwords at this moment.
dirtydodge said:
ok. Yea i would try that. I can't duplicate the issue on my end. Leave the ro.secure storage set to true and see if that fixed it. That's what mine is set at and I'm not having any problems with Bluetooth or passwords at this moment.
Click to expand...
Click to collapse
I have reflashed the rom and also added a dual speaker mod. Everything is working like a charm. Bluetooth and Wifi are all working.
Flashed this and it works fine, but I also experience WiFi 'losing' passwords.
I just flashed it again and no change. In fact, from the time I enter the WiFi password during setup until setup is done, I have to re-enter WiFi password because it 'forgets' (it reports authentication error later after having worked fine initially)
Any other ways to fix this so I don't have to keep re-entering passwords like this?
JJHiemenz said:
Flashed this and it works fine, but I also experience WiFi 'losing' passwords.
I just flashed it again and no change. In fact, from the time I enter the WiFi password during setup until setup is done, I have to re-enter WiFi password because it 'forgets' (it reports authentication error later after having worked fine initially)
Any other ways to fix this so I don't have to keep re-entering passwords like this?
Click to expand...
Click to collapse
Use root explorer, go to system/build.prop and make sure ro.secure.storage is set to "true" as shown in the attachment. I live around Houston TX so we're prepping for the hurricane at the moment so I might be oit for a few days but I'll try to check back on here as soon as I can. Another issue that has been brought up is the phone forgetting Bluetooth device after a reboot. At this moment there is no fix for it that i can find. As soon as I can find a fix for this i will upload a new version.
same g930a-v models-same problem.pls wanted phone emergency backup file (g930a-v same
same g930a-v models-same problem.pls wanted phone emergency backup file (g930a-v same).help me pls all user phone no down mode.
http://forum.gsmhosting.com/vbb/f10...0a-sbl-error-upload-mode-pls-help-me-2301220/
dirtydodge said:
This is my first ever ROM to post up. I just recently started building them. This is a stock deodexed Nougat ROM that is pre rooted. It is 100% AT&T Nougat with just a few fixes. I have left all Samsung and AT&T bloat for those that want all the bloat but like to be rooted and deodexed.
Follow the steps below for installation:
Step 1: You must already be on Nougat firmware. There are various threads on how to do this but if you can not figure it out just ask and i will try to assist you the best i can.
Step 2: Once on Nougat, root your device. Follow this guide https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Step 3: Once Rooted, install Flash fire from playstore.
Step 4: Open Flashfire and grant SuperSU access, once you are at the main menu, press the + and select Flash ZIP or OTA, go to the place you stored the ROM and selecet it. On the next screen MAKE SURE "Mount /system read/write" is selected and click the check mark in the upper right hand corner.
Step 5: Click the + sign again and select "Wipe", leave the defaulted boxes checked (System data, 3rd party apps, and Dalvik cache) and click the check mark in the upper right corner again. ( optional, you can select internal storage but you don't have to).
Step 6: VERY VERY IMPORTANT, select and hold down on Wipe and move it above "Flash ZIP or OTA"
Step 7: Make sure EverRoot is disabled and Reboot is set to normal.
Step 8: Click the lightning bolt and then yes on the next prompt, and let FF do it's thing.
*****Be patient, it will take up to 15 min to boot but most times it is quicker than that.*****
* Fixes i added
Fingerprint fix after root. Thanks to @qwewqa
Replaced IMSService.apk to remove hurricane icon.
CPU Fixes. Thanks to @stang5litre
Issues:
Phone forgetting Bluetooth devices after reboot, I am trying to find a fix for it and will update when i do.
Thanks @stang5litre for countless hours and days of walking me through so many steps from setting up my kitchen to fixing my phone via TV and ADB.
Thanks @SuperR. for the kitchen and all the continued support
Thanks @Chainfire for Flashfire and SuperSU
Download link: https://www.dropbox.com/s/17w8ut192jwixnw/G930AUCS4BQE1.zip?dl=0
Click to expand...
Click to collapse

Question Navigation buttons stop working

I'm on the January update. I'm using 3 button navigation. In the last day, the buttons have stopped working multiple times. When I reboot my phone then the buttons work again.
I am rooted and using Magisk add ons by @Typhus with ROM control.
Anyone else seeing this?
My wife uses 3-button navigation (I use gestures). She's unrooted and using Nova Launcher. She said she hasn't had that issue.
swieder711 said:
I'm on the January update. I'm using 3 button navigation. In the last day, the buttons have stopped working multiple times. When I reboot my phone then the buttons work again.
I am rooted and using Magisk add ons by @Typhus with ROM control.
Anyone else seeing this?
Click to expand...
Click to collapse
I'm still on December and the 3 button navigation is broken as you describe it. Since you're seeing it in January I'm not in such a big hurry to update now. I am so pissed off at Google!
almahix said:
I'm still on December and the 3 button navigation is broken as you describe it. Since you're seeing it in January I'm not in such a big hurry to update now. I am so pissed off at Google!
Click to expand...
Click to collapse
Are you running any magisk modules? I thought that might be related to what I am seeing.
swieder711 said:
Are you running any magisk modules? I thought that might be related to what I am seeing.
Click to expand...
Click to collapse
Magisk for root but no other modules
I think it's not magisk related
And I'm also experiencing this on gestures
Swiping up sometimes just does nothing and is really annoying
Edit: stock on Jan update
Iam on standard January update phone no root i have no working navigaton buttons few times per week its normal issue on pixel 6 pro for now just wait for update
superman25 said:
Iam on standard January update phone no root i have no working navigaton buttons few times per week its normal issue on pixel 6 pro for now just wait for update
Click to expand...
Click to collapse
That's what they said in December! How long will we wait until they get things working?
Even though I had no confidence that it would be resolved in the January release I tried unsuccessfully to side load the Jan OTA. The system update failed to update and for some reason I could never get adb sideload to work so I used the Android Flash Tool to install January, which of course wiped my phone. After all these years I have procedures in place that allow me to recover when that happens, which require me to root. (I miss my reliable OnePlus 7 pro.)
almahix said:
That's what they said in December! How long will we wait until they get things working?
Even though I had no confidence that it would be resolved in the January release I tried unsuccessfully to side load the Jan OTA. The system update failed to update and for some reason I could never get adb sideload to work so I used the Android Flash Tool to install January, which of course wiped my phone. After all these years I have procedures in place that allow me to recover when that happens, which require me to root. (I miss my reliable OnePlus 7 pro.)
Click to expand...
Click to collapse
I've been under the impression from others who used the Official Google Android Flash Tool that there is an option to prevent wiping you can select. I haven't used the site myself, I do it using the script in the full factory image using the latest Platform Tools each month, editing the script first to eliminate the "-w " so the phone isn't wiped.
I never use OTAs while rooted, just flash the full factory image instead.
roirraW edor ehT said:
I've been under the impression from others who used the Official Google Android Flash Tool that there is an option to prevent wiping you can select. I haven't used the site myself, I do it using the script in the full factory image using the latest Platform Tools each month, editing the script first to eliminate the "-w " so the phone isn't wiped.
I never use OTAs while rooted, just flash the full factory image instead.
Click to expand...
Click to collapse
I'll try that way next time I can't update.
My 6 will do that. They just stop responding. Myself I don't need to reboot though. Either I can wait for a few seconds and they'll start working again, or at most lock then unlock the phone.
I had the same issue all the time on December update. A reboot would fix it but I have not seen it all on January update..
I had that problem with December's build, but so far it hasn't happened with January's.
Using 3 button myself on Jan update. Also use Nova and have had no issues. It was a clean install though.
I have a OP8 with a custom a11 ROM on it that 3 button navigation has worked flawlessly on. I upgraded it to 12 over the weekend and have had the buttons lock up a couple of times since. So it would appear to be a a12 thing, and not just a a12 on Pixel issue.

General S1SC32.52-69-16 Update - Lock Screen issue - SOLVED

Guys, do not take OTA update April (375 MB), it has issue with the lock screen.
You will not able to go to homescreen once you put the phone locked (or screen off) , you need to forced reboot the phone to be able to go to homescreen.
I'm downgrading to earlier version
SOLVED, update the firmware (July Security update) and then Go HERE
I can the update and no problem for me. All works ok
mythras73 said:
I can the update and no problem for me. All works ok
Click to expand...
Click to collapse
something wrong with my phone? I flashed earlier firmware then took the ota update still got the same issue.
I can update and all iits o.k.
my lock screen issue
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse
nice info.. I will try it
Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse
just try it, and keeps doing the same issue.
Hi! I also have a lock screen issue, and now I can only downgrade
Blade^ said:
鎖屏也有這個問題。只需進入自定義功能即可關閉窺視顯示並重新打開以使其正常工作
Click to expand...
Click to collapse
這個方法沒用
zlebors said:
nice info.. I will try it
Click to expand...
Click to collapse
This method is useless
Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse
NFC use or not
Download the XT2201-6 firmware there
zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse
KenHuang2022 said:
NFC use or not
Click to expand...
Click to collapse
NFC Working
KenHuang2022 said:
This method is useless
Click to expand...
Click to collapse
Weird it worked for me. But I also tried changing the peek display from weather display to just battery. Can try that too.
Had the same issue 1st reboot after update, had to reboot via long press power. But since then seems to be working ok.
BTW, it looks like "Google Play System Update" disappeared from Security menu, now i see only stock security update here.
A long press on the power button doesn't respond to any mechanism. You can only reboot by volume and power on mechanism.
Maybe the baseband is broken, because I have flashed dozens of times
zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse
where do you download the firmware S1SF32.22-16-14-19?

Question Auto dimming issue ?

Hi everyone,
I have have some weird issue recently with my Pixel 6Pro...
When I've got my phone in a pocket and somebody is calling me, after taking the phone out of the pocket screen is very dark/dimmed and it takes quite a long time for it to brighten up.
Very annoying as I never see who's calling and can't even see the toggle to pick up call.
Never had that before, just appeared out of nowhere a few weeks ago...
I've tried to reset adaptive brightness, still didn't helped...
Anyone got any clue or had this issue as well ?
Thanks
@Maple1 I haven't seen this issue. Is it possible that some recent app you've installed is interfering with it? Are you rooted, using any Magisk or LSposed Modules, or custom kernels?
roirraW edor ehT said:
@Maple1 I haven't seen this issue. Is it possible that some recent app you've installed is interfering with it? Are you rooted, using any Magisk or LSposed Modules, or custom kernels?
Click to expand...
Click to collapse
Complete stock system, not rooted etc. and I don't recall any freshly installed applications that could trigger this somehow <hmm>
Maple1 said:
Complete stock system, not rooted etc. and I don't recall any freshly installed applications that could trigger this somehow <hmm>
Click to expand...
Click to collapse
The only other things I can think of to try is a factory reset, or even Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). The official Android Flash Tool has solved issues for at least dozens of people that I've seen in this phone section alone, including me, when even the full factory image didn't help. Note that the flash tool will wipe your phone due to the fact that it has to unlock your bootloader in order to function.
Obviously, if you have a version of the Pixel 6 Pro that you can't unlock the bootloader on, then the official Android Flash Tool is not an option for you.
Maple1 said:
When I've got my phone in a pocket and somebody is calling me, after taking the phone out of the pocket screen is very dark/dimmed and it takes quite a long time for it to brighten up.
Very annoying as I never see who's calling and can't even see the toggle to pick up call.
Click to expand...
Click to collapse
Yep had this since I can remember, usually a tap on the screen will bring it to life but it can be slightly annoying. You are not alone.

Categories

Resources