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.
Related
Over the last several weeks (possibly since the last update), my Launcher feeds aren't consistently displaying. I just get a blank Google screen when I swipe left.
If I open the Google app, then the feeds show up. Refreshing the screen isn't correcting the issue, and I confirmed my settings are all turned on.
Happening to me also.
Deleted data/cache fixes it temporarily
Same here, I just reboot and it works for a while
Same here, usually if I clear cash and stop app then go back and swipe everything pops back up. Weird, thought it was just me.
Sent from my Pixel XL using Tapatalk
A.VOID said:
Over the last several weeks (possibly since the last update), my Launcher feeds aren't consistently displaying. I just get a blank Google screen when I swipe left.
If I open the Google app, then the feeds show up. Refreshing the screen isn't correcting the issue, and I confirmed my settings are all turned on.
Click to expand...
Click to collapse
I had this same issue myself and I actually used the google help and after trying everything I ended up going to settings then apps go to Google app or you can go to play store and google app then disable and uninstall updates then reinstall and reboot after doing it and it has seemed to completely fix the problem for me this is going on the third day it has not randomly disappeared on me. I hope it helps guys.
Reporting back that ruling back Google and updating it again has fixed it so far. Hopefully it holds
Same here. Google is turning into a ****ing joke. This is the 4th update this month that ****s something up for me.
The security patch has literally ruined Bluetooth usage for me. Then they update Chrome and I can no longer cast embedded videos from Chrome. Then I get the Google update and it screws up the feed. Now I get the music update and it kills the equalizer almost all the goddamned time.
What a ****ing joke.
After 24 hours, it failed again ?
AndrasLOHF said:
Same here. Google is turning into a ****ing joke. This is the 4th update this month that ****s something up for me.
The security patch has literally ruined Bluetooth usage for me. Then they update Chrome and I can no longer cast embedded videos from Chrome. Then I get the Google update and it screws up the feed. Now I get the music update and it kills the equalizer almost all the goddamned time.
What a ****ing joke.
Click to expand...
Click to collapse
Enjoy famed frequent Google updates.
A.VOID said:
After 24 hours, it failed again
Click to expand...
Click to collapse
Same here. Best bet probably is going to be reverting back to the previous apk and turning off updates until they fix it. It's what I had to do for Google Play Music.
A.VOID said:
Over the last several weeks (possibly since the last update), my Launcher feeds aren't consistently displaying. I just get a blank Google screen when I swipe left.
If I open the Google app, then the feeds show up. Refreshing the screen isn't correcting the issue, and I confirmed my settings are all turned on.
Click to expand...
Click to collapse
Cryingmoose said:
Happening to me also.
Deleted data/cache fixes it temporarily
Click to expand...
Click to collapse
jaben2 said:
Same here, I just reboot and it works for a while
Click to expand...
Click to collapse
ahent said:
Same here, usually if I clear cash and stop app then go back and swipe everything pops back up. Weird, thought it was just me.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
This is a known issue with the Google App. Can only assume it will eventually be fixed in an update.
OMG! ok.. i'm not going insane... it's happening to other people too... whew...
SquallLHeart said:
OMG! ok.. i'm not going insane... it's happening to other people too... whew...
Click to expand...
Click to collapse
Mine seems to be working fine. Maybe they fixed it
My screen flashes when the screen locks. It does this for a bit and then just randomly stops doing it, until it starts again. I've contacted Google and they won't let me do an RMA saying it's a known issue and should be fixed in a coming update. Anyway else have this issue?
acheney1990 said:
My screen flashes when the screen locks. It does this for a bit and then just randomly stops doing it, until it starts again. I've contacted Google and they won't let me do an RMA saying it's a known issue and should be fixed in a coming update. Anyway else have this issue?
Click to expand...
Click to collapse
The issues been around as far back as November but I've never experienced it.
EeZeEpEe said:
The issues been around as far back as November but I've never experienced it.
Click to expand...
Click to collapse
Is there any known fix?
acheney1990 said:
Is there any known fix?
Click to expand...
Click to collapse
A monthly update is supposed to address it eventually.
http://piunikaweb.com/2018/02/09/fi...hing-flickering-issue-reportedly-coming-soon/
EeZeEpEe said:
A monthly update is supposed to address it eventually.
http://piunikaweb.com/2018/02/09/fi...hing-flickering-issue-reportedly-coming-soon/
Click to expand...
Click to collapse
Well hopefully. Thanks.
Well I'm running the April update and the flashing issue returned today again. Still no fix. Ugh.
Mine started doing it after the April update. I started uninstalling a bunch of apps (like rotation control) thinking it was causing the issue. But nope...
Clearing cache and data, disable, & re-enable helps.
foeshigity said:
Clearing cache and data, disable, & re-enable helps.
Click to expand...
Click to collapse
But I've even tried resetting the phone as well as flashing system image, still does it.
acheney1990 said:
But I've even tried resetting the phone as well as flashing system image, still does it.
Click to expand...
Click to collapse
I think I've seen this just one time for me. It's consistently happening every time? Does this happen in safe mode?
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
I think I've seen this just one time for me. It's consistently happening every time? Does this happen in safe mode?
Click to expand...
Click to collapse
Not happening all the time. Does it for like 10 mins then stops for a week or two before randomly doing it again.
It's infuriating, as people keep thinking I'm taking their photo. Anyone heard anything more about a fix?
Long discussion in Pixel product forum. No fix helped yet. I have heard that Google isn't allowing replacements because of the flashing; which hopefully means that they are working on a fix.
We'll have a new security update in a few days - I have everything crossed!
My XL started doing it today. Think I updated yesterday to the 5 May patch.
Just rebooted and it stopped. But I'm sure it will return
I am on the P beta and so far the screen flickering disappeared.
mgymnop said:
I am on the P beta and so far the screen flickering disappeared.
Click to expand...
Click to collapse
I am too. Fingers crossed! :good:
Same here... Good so far.
Any updates on this? Still good on P beta? I have a brand new 2 xl (Literally 5 days old) and just started experiencing this today. Should I just wait for P to release or should I go back to the verizon store and get a replacement?
I just picked up the XL 2 yesterday and my screen started flashing today. Called Google support and they said it is a software issue and that they are working on a fix for it and will roll it out in an update. Seems rather strange they've heard about this for 6 months and still no update as of yet. My bet is that this "fix" is Android p.
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
kickenwing13 said:
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
Click to expand...
Click to collapse
I have noticed this sometimes as well on DP2. I have a fingerprint setup but my phone is usually lying on my desk so i swipe up and enter the pattern. Sometimes it just refuses to swipe up and stay there.. its sort of bounces back down. I have to pick up the phone and use the fingerprint scanner.
They lock screen swipe issue was fixed for me recently on a security update but on dp2 sometimes it's worst then it ever was before the fix.
Just tap the lock, no need to swipe
Ah never noticed that. If you have the fingerprint enabled, tap the fingerprint icon.
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
And this is why you're a senior member, that's pretty helpful. Now swiping away notifications would be wonderful
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
Are they not allowed to test and provide feedback? Why does it bother you?
Anyways, to be fair, I've been experiencing this issue off and on ever since I purchased the phone. And no, I'm not running beta firmware.
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
The lockscreen swiping is definitely an issue with the Pixel 2 XL. I always had this issue on Oreo but on P DP2 it's gone. It's interesting how it's the opposite for others in this thread.
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
E30Nova said:
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
Click to expand...
Click to collapse
Oreo Lock Screen Fix (Substratum) from Arol Wright fixed it for me.
skimminstones said:
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
Click to expand...
Click to collapse
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
To be fair....even before I jumped on dp2....I had these same lockscreen issues on Oreo. It's just worse on dp2.
kickenwing13 said:
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
Click to expand...
Click to collapse
Nope, No issues on mine
Yeah the swipe up issue definitely does happen once in a while for me but it's not often or consistent. Now that I know the tap the fingerprint/lock does the same thing, I just do that.
Sent from my Pixel 2 XL using Tapatalk
No issues here. If i'm looking for perfection ill go purchase one of those $25,000 phones and even then you'll find something wrong.
PROBLEM SOLVED
Mate 20X (EVR-AL00; Build no. 9.0.0.136). I left my phone at home while downloading the new games via our Wi-Fi. But when I got back, I noticed that it has not downloaded any more data since I left it.
The culprit? The option Stay connected when device sleeps under the battery settings is DISABLED (neither ON nor OFF). Anyone else has this experience? What can be done about it?
------------------------------
TRY THIS:
AngelDeath said:
@the_passerby5981 I figured it out, and boy your going to hate sending yours back, I was right, it is tied to something. I kept thkinking and kept coming back to this thread knowing you and I were missing something, and I found it from your screenshot and others, then tested it on mine and bingo. The reason its disabled is because it is tied to the SIM card. So that setting is tied to a sim card, and it didnt work on yours or mine because we were both testing it out without a SIM, and as soon as I put mine in to see if I was right, it enabled to turn on or off.
Click to expand...
Click to collapse
the_passerby5981 said:
BUG FOUND! (Problem solved).
Android 8 had the option under WLAN and option to disable staying connected to WLAN and MOBILE as separate.
In Android 9, they are baked together under Battery. Thus, Stay awake when device sleeps gets DISABLED WHEN NO SIM IS INSERTED.
Click to expand...
Click to collapse
Moderators, please close the thread. I seem to not have enough privileges to do it myself.
Mine was checked on but a good one to know. Need a good week to really go thru the settings and get them set how you like. Like a maze with secret passages.
the_passerby5981 said:
Mate 20X (EVR-AL00; Build no. 9.0.0.136). I left my phone at home while downloading the new games via our Wi-Fi. But when I got back, I noticed that it has not downloaded any more data since I left it.
The culprit? The option Stay connected when device sleeps under the battery settings is DISABLED (neither ON nor OFF). Anyone else has this experience? What can be done about it?
Click to expand...
Click to collapse
Thanks for the info that's been pissing me off for awhile now
Cccmachins said:
Mine was checked on but a good one to know. Need a good week to really go thru the settings and get them set how you like. Like a maze with secret passages.
Click to expand...
Click to collapse
Did you do it yourself? Or did it come that way?
the_passerby5981 said:
Did you do it yourself? Or did it come that way?
Click to expand...
Click to collapse
Strange I have the same phone as you with the same update and I have the option to turn it on and off.
On EVR-L29 it was off, so i turn it on myself now Thanks.
the_passerby5981 said:
Did you do it yourself? Or did it come that way?
Click to expand...
Click to collapse
I think I had to turn it on. Been over a week since I got it. Changed so much stuff can't remember. Old-timers setting in.
hughey2k2 said:
Strange I have the same phone as you with the same update and I have the option to turn it on and off.
Click to expand...
Click to collapse
Look!
the_passerby5981 said:
Look!
Click to expand...
Click to collapse
That's a beach. AL00 here 136 and I still have the option to turn on or off. Ain't playing with or I'll lose mine. Or go blind
---------- Post added at 08:53 PM ---------- Previous post was at 08:30 PM ----------
Goofy ass Hicare iPhone wanna be says I feel your pain and rest your phone. I wanted to tell her to go where the sun doesn't shine but just doing her job. But she maybe right. May have to reset
the_passerby5981 said:
Look!
Click to expand...
Click to collapse
That's really strange have you ever restarted the phone since the new update. If that doesn't work you can try to reset all settings and see if that works there's no reason why yours is blocked and other people's aren't unless you have some kind of aggressive battery manager or something.
hughey2k2 said:
That's really strange have you ever restarted the phone since the new update. If that doesn't work you can try to reset all settings and see if that works there's no reason why yours is blocked and other people's aren't unless you have some kind of aggressive battery manager or something.
Click to expand...
Click to collapse
Resetting the settings did nothing. Gonna give a shot at resetting the phone. I didn't tinker with any other settings coz I wanted the phone to be up and running at once. It only happened that I hit a snag with this issue.
TAKE NOTE: My unit is running on a "China ROM".
hughey2k2 said:
Thanks for the info that's been pissing me off for awhile now
Click to expand...
Click to collapse
Do you also have an EVR-AL00 running on 9.0.0.136?
the_passerby5981 said:
Do you also have an EVR-AL00 running on 9.0.0.136?
Click to expand...
Click to collapse
Yeah I have the same phone.
same, able to change no problem
I tried last night to toggle thinks on and off to try to get mine to gray out. I couldn't. I tried again with HiCare but he needs some info for your phone. Give them a try. You need that option.
the_passerby5981 said:
Mate 20X (EVR-AL00; Build no. 9.0.0.136).
The culprit? The option Stay connected when device sleeps under the battery settings is DISABLED (neither ON nor OFF). Anyone else has this experience? What can be done about it?
Click to expand...
Click to collapse
I also have the EVR-AL00 with Build Number 9.0.0.136. I have no problem to enable/disable the option. See the pictures.
hughey2k2 said:
Yeah I have the same phone.
Click to expand...
Click to collapse
Just to clarify, you have the same phone and build number as mine, AND the same experience? Cannot toggle "Stay connected when device is asleep" ON/OFF?
the_passerby5981 said:
Just to clarify, you have the same phone and build number as mine, AND the same experience? Cannot toggle "Stay connected when device is asleep" ON/OFF?
Click to expand...
Click to collapse
Yes I have the same Phone and build number but I can toggle the "stay connected when device is asleep"tab on and off
1. So, there are about 5 users here with the same model number (EVR-AL00) and build number (9.0.0.136). Some can toggle "Stay connected while device sleeps", while--like me--hughey2k2 cannot. I cannot.
2. If it were a software problem, then all of us should have the same experience.
3. Does this point to, possibly, a hardware-related problem peculiar to the specific production batch? (Just to spell it out I mean, hughey2k2's phone were produced in the batch and there was a problem in production--possibly hardware--that could be the cause).
Comments?
EDIT: hughey2k2's unit does not have the same problem.
hughey2k2 said:
Thanks for the info that's been pissing me off for awhile now
Click to expand...
Click to collapse
If you can toggle ON/OFF, then what is pissing you off about it?
after each lock when i turn the screen on with double tap or power button screen is unresponsive for good 3 seconds. This started happening after the latest camera fix update. When if i use aod and use the fingerprint through the aod this doesnt happen. tried reboot and factory reset with fresh install (no backups) tried safe mode. Same thing happens.
S20 plus exynos.
Yup happening to me too (s20+ exynos). For me the time of unresponsiveness is around 1-2 seconds. Happened after the latest update.
Yes, have been facing the same issue since "ATCH" update.
Yeah has been driving me nuts. Same problem.
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Glad to see it's not only my device. Waiting for fix.
I have similar situation
I'ne noticed the same after the last update.
Chris_c81 said:
Yeah has been driving me nuts. Same problem.
Click to expand...
Click to collapse
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
Chris_c81 said:
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Click to expand...
Click to collapse
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
anfederin said:
I have similar situation
Click to expand...
Click to collapse
Mine is Exynos
sjandroiddeveloper said:
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
Click to expand...
Click to collapse
Is there any channel to communicate this bug to Samsung? Anyone know?
Chris_c81 said:
Is there any channel to communicate this bug to Samsung? Anyone know?
Click to expand...
Click to collapse
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
sjandroiddeveloper said:
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
Click to expand...
Click to collapse
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
turn off the battery optimized for apps: com.samsung.android.biometric.
Go to Settings>Apps>Select "Special Access" from three dot menu>Optimise Battery Usage>select All from drop down menu>Search for "com.samsung.android.biometric"> Turn it off and Restart.
Click to expand...
Click to collapse
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Did accordingly as above.
For a moment it felt like the issue is resolved!
But after checking several times I can confirm the issue still exists.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Sent from my SM-G986B using Tapatalk
verynuclear said:
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Click to expand...
Click to collapse
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Virgo_Guy said:
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Click to expand...
Click to collapse
Have you restarted the phone? It didn't work until I restart mine.
Sent from my SM-G986B using Tapatalk
verynuclear said:
Have you restarted the phone? It didn't work until I restart mine.
Click to expand...
Click to collapse
Ofcourse I did. In fact restarted one more time since it didn't resolve after the first restart, post disabling the optimization.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
I did this already and while it feels like fingerprint is faster, unfortunately this is a screen issue. You see if the screen is off and i put the finger in the correct spot it always scans my finger without any lag. The issue is occurs when -
a) I have unlocked the phone using above way, then the screen becomes unresponsive right after unlocking.
b) The screen is off and i either press the power button or double tap to wake, then the screen will be unresponsive and its during this time the fingerprint scanner doesn't scan (because the scanner doesn't know it needs to scan since the touch is unresponsive)
so TL;DR its not a FP scanner issue.
I am quiet sure Samsung is already addressing this issue for next update.