I came form an S8+ and never saw this crap before. I did see mention of it on an S10 in a post on reddit and the solution was apparently "disable "strong protection" in biometrics advance settings". But this option doesn't exist on my ultra. I don't want to faff about unlocking the thing every morning when I turn it on just to be able to see if any notifications have turned up. It is also not booting fully until I unlock it because it comes up with "starting phone" afterwards and I then have to wait another couple of minutes after that for all the notifications to have arrived. It's ridiculous. There MUST be a way to turn this **** off and have the thing just boot normally! There has to be an obscure option somewhere that I haven't seen?? I can't even find mention of this on google so perhaps I am the only one in the world this happens to.
I have the same issue. But can’t find any solution.
Related
Hi,
When i get a call and i click on "decline" button, i should get a pop up allowing me to send a quick message or make a reminder about calling back.
I checked and the relevant options are ticked on in the phone settings section.
What happen though is that i decline the call and the pop up shows for a split second and disappear :\
I attached a picture of the evasive pop up.
I tried ticking the option on and off, rebooting, nothing helps.
The only thing that seemed like it changed was resetting the phone (on power menu, you can reboot and delete temp files or something like that). That made the feature work once, but on the seconds time i declined a call it dissapeared again.
I did make sure the "Don't show this again" option is UNCHECKED.
I searched XDA forums and google, and only found one relevant topic which did not solved my issue.
Help...?
yrufset said:
Hi,
When i get a call and i click on "decline" button, i should get a pop up allowing me to send a quick message or make a reminder about calling back.
I checked and the relevant options are ticked on in the phone settings section.
What happen though is that i decline the call and the pop up shows for a split second and disappear :\
I attached a picture of the evasive pop up.
I tried ticking the option on and off, rebooting, nothing helps.
The only thing that seemed like it changed was resetting the phone (on power menu, you can reboot and delete temp files or something like that). That made the feature work once, but on the seconds time i declined a call it dissapeared again.
I did make sure the "Don't show this again" option is UNCHECKED.
I searched XDA forums and google, and only found one relevant topic which did not solved my issue.
Help...?
Click to expand...
Click to collapse
You might just have to do a complete factory reset. Sometimes, system functions can get screwed up for no apparent reason (it is usually something else you installed). Are you stock or on a custom ROM?
Hi, thanks for your reply.
I guess that deep inside me, i knew you would recommend that...
The device is new. Bought it last week. it's stock, unrooted, untouched.
I did a lot of rom changes before with my other device (GS3) so i'm no stranger to factory reset, but every time i used it was to completely change a rom. I have never done it on a brand new device in order to actually reset a glitch...
Can you tell me what exactly will factory reset delete? What will i loose? any personal data? apps? app setttings? what else?
Thanks :cyclops:
I get a "Sleep Record" notification every morning (ever since I got this device a couple weeks ago), which is really stupid because I leave the watch on the charger all night, every night.
<rant>
Really Samsung? Your software tells me about how good my sleep was while the device was charging on the nightstand? Yeah, I didn't move all night! I slept like a rock! ..... Is it that hard to code an app to be able to tell that when the watch is on the charger it is NOT in the person? Or how about coding the app so that the user can disable all sleep recording functions and the related notifications? I've searched this problem, and it's been an issue for quite a while, but Samsung support people tell users to factory reset their device, multiple times! (yeah, that really makes things better, for most of us who spend a while setting this up to our liking) Why don't they instead admit that their developers did something dumb and then they can work toward a fix? (sorry, but as a software developer, I see this kind of denial all the time)
</rant>
So now I hope this is something in the past, and maybe someone in the know can tell me it was finally fixed.
In Samsung Health app's "Settings", I have notifications disabled for the entire app.
In Samsung Health app's "Manage Items" I have "Sleep" disabled.
What more is needed?
Any XDAers figure this one out?
I don't know exactly what I did that made this start happening, but right now every time a toast message pops up it stays on the screen for over 10 seconds. If there are other messages queued up then it will display all of them one after another each for over 10 seconds. I did a Google search and could not find a solution. Has this happened to anyone else?
I've tried everything short of a factory reset. I rebooted and safe mode and it still happens. I reset all of the application preferences, as far as permissions and that sort of thing goes, that fixed a few issues I've been experiencing but the toast problem persists.
Is this a bug? is there a solution? Can you adjust the timeout for toast messages? Are there any third party apps that change this setting on an unrooted phone that I unwittingly may have used?
Will I be forced to do a full factory reset to fix this problem? It's really annoying, haha!
thanks in advance for any help
I did everything including a factory reset and those toast messages still did the same thing, so I am thinking it definitely is an OS system upgrade problem!!! It is so annoying !!
twowreally said:
I did everything including a factory reset and those toast messages still did the same thing, so I am thinking it definitely is an OS system upgrade problem!!! It is so annoying !!
Click to expand...
Click to collapse
I still don't understand if this happens on everybody's Pixel 3 or if it's just ours. if it's just a few people then there has to be a common thing that caused it to start doing this. I haven't thought about it too much but my first suspicion was SystemUITuner. did you by chance install that and change anything using it?
I can't think of anything else that I have had to enable permissions with ADB for on here that would have messed with the display settings.
I've been rooting every phone I owned since cupcake. usually owning more than one at a time because well that just makes your power level go up exponentially ... through carelessness and not reading what I needed to before purchasing my Verizon Pixel 3 XL, This is the first phone I've had in my life for more than a month or so that was a daily driver without root.
my point is, I really can't think of a reason why the timeout for all toast messages system wide would suddenly change to be 30 seconds long instead of three. I would have bet on it that that is something that you need root to alter. ??*
typos are speech to text
Sent from my Google Pixel 3 XL using XDA Labs
looking at Google's past release schedule and also starting to hear rumors about Android 11 (they did put a system image up on Google's page but you cannot install it without an unlocked bootloader), we should start hearing official announcements about it soon, with beta1 probably end of April beginning of May.
Even if there are a few not annoying bugs I think it would be worth the upgrade to get rid of these toast messages covering all kinds of stuff that I need to be reading NOW! not in (in the case of three or four toasted pop-up great after each other) 2 minutes later when I've already Ben distracted and can't remember what I was wanting to be able to tap on that was under the eternal-1 toast message timeout.
it's very interesting to me that if you Google this problem there's maybe one or two results. I'm very curious what we are doing to cause this issue. if you or anyone from the future is reading this and knows This information please leave a little response or just post a link it, so maybe I can die happy having finally solved this riddle
thank you in advance
Sent from my Google Pixel 3 XL using XDA Labs
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.
testbug said:
... it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Click to expand...
Click to collapse
Oh my, thank you so much, I had the same problem and this solved it!!!
I wish there was a way to make it shorter than 3 seconds but from my research it can not be changed can it?
syndre said:
looking at Google's past release schedule and also starting to hear rumors about Android 11 (they did put a system image up on Google's page but you cannot install it without an unlocked bootloader), we should start hearing official announcements about it soon, with beta1 probably end of April beginning of May.
Even if there are a few not annoying bugs I think it would be worth the upgrade to get rid of these toast messages covering all kinds of stuff that I need to be reading NOW! not in (in the case of three or four toasted pop-up great after each other) 2 minutes later when I've already Ben distracted and can't remember what I was wanting to be able to tap on that was under the eternal-1 toast message timeout.
it's very interesting to me that if you Google this problem there's maybe one or two results. I'm very curious what we are doing to cause this issue. if you or anyone from the future is reading this and knows This information please leave a little response or just post a link it, so maybe I can die happy having finally solved this riddle
thank you in advance
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Just an FYI, coming from AT&T prepaid 6 years during the covid party the depth AT&T is it has taken me 9 months to move to postpay. It is a corporation a complete morons above customer support. All my problems are met with an upsell attempt and I have bit once or twice in return I was kindly bitten all this to say that they put a Motorola one 5G Ace 64 4G ram in my hand and I have the same issue except might hang for 20 to 45 seconds it seems like 90 seconds! May well be. Obviously they're not translucent but the desktop or any operation underneath it will take a finger command if you know where the hell to push. I did not get it from Amazon but I was looking to upgrade to the 128 prior and post this phone and one of the main salesman there with Motorola America which of course is not a Motorola product it's just a Motorola name. The ruination of a long-standing pioneer groundbreaking company! and he wanted to know more information from me and wants me to become a free paid intern or some crap and help them figure out what's going on so there you go? I am sure I am not the only one and just as sure as I am of that, I am sure that the people that make them and sell them and talk about them all day to potential customers or two customers have no freaking idea what their products do.!!
metpet said:
Oh my, thank you so much, I had the same problem and this solved it!!!
Click to expand...
Click to collapse
testbug said:
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.
Click to expand...
Click to collapse
dude... thank you.
i dunno how leaving a toast message on top of the buttons you need TO take action helps but that is what caused, likely, or at least what corrected the issue for me.
Moto G7 Supra (Power)
testbug said:
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.II
Click to expand...
Click to collapse
I can't find this accesability option on my note 10 + g975fd bubi know it was some kind of setting somewhere because I remember turning it on trying to see some message it waS throwing while I was setting up some Tasker task. Which makes me think it might have been turned on by option for a tasker action but I'll be damned if I can find it again. It's actually nice most of the time but lately it's been really annoying to me because it shows over the keyboard and most of the time an OK or cancel prompt. And like previously mentioned if there are ten of them its quite a long time to wait. And I also turned something on that does a toast every time an intent is launched so you can see how this has multiplied the issue. I think it's one of those situations like (in Tasker you can say launch so n so app, one of the potions is to make the app launch a new instance and another is to have the app not appear in recents. That's all fine gravy for that instance but nobody anywhere ever says that from now on any time you launch that app that it will launch a new instance and it won't appear in recents) whether it's in Tasker or from the Launcher or if you just switch to another app and back. It quickly becomes an issue when you are trying to enter passwords or watch Netflix and do something else real quick. And if you don't put 2 together with 2 because you didn't notice right a way it can be a brain bender trying to figure the little problem out. I'm thinking that's what I have done is set some obscure option for God knows what experimental task and now its stuck that way. But it's really not something I want to bother joã (Tasker de"sorry for spelling") with and he may not know anyway. But thanks for the thread and any other suggestions would be appreciated.
Hi,
I find the Smart Lock (using Trusted Places) to be very buggy..
Sometimes I find that the Smart Lock just stops working when I'm at my desk.. Whatever, so I try and re-enable it, but I'm never able to easily re-enable it. I follow the same process, but the lock screen doesn't have the unlocked padlock. Rebooting the device made it work, and I also got it to "work" by toggling "On-body detection", and then going back to "Trusted places" (or some odd combination of adding a 2nd Trusted Place). It's a bit frustrating..
It's also not clear to me how to enable the "Trusted places" option. For example, the "On-body detection" option has a toggle to enable it. The "Trusted places" screen has no button/toggle. I tap on the big tile/graphic of the "house with the 4 dots linking to the phone", and I believe that's how you kickstart it?
Lastly, in the Trusted Places screen, it has a note at the bottom saying:
"Your device will stay unlocked for up to four hours..."
Click to expand...
Click to collapse
So according to that, it expires at 4 hours? However when I wake up I notice that it's still active..
I have a similar issue were at random the smart lock will just not work and I have to log back into the phone, even finger print option not available. Basically same as if I was to restart the phone. The feature is still enabled so don't need to re enable! I was hoping that getting onto a pixel this garbage will stop happening after experiencing it on my old op6t but as of now the pixel works worse then op.
thisguy159 said:
I have a similar issue were at random the smart lock will just not work and I have to log back into the phone, even finger print option not available. Basically same as if I was to restart the phone. The feature is still enabled so don't need to re enable! I was hoping that getting onto a pixel this garbage will stop happening after experiencing it on my old op6t but as of now the pixel works worse then op.
Click to expand...
Click to collapse
Ah interesting, so you are experiencing similar issues too..
I wonder if it has something to do with the phone temporarily losing it's current location, and thus forcing a lock on the phone? Not sure..
oksureman said:
Ah interesting, so you are experiencing similar issues too..
I wonder if it has something to do with the phone temporarily losing it's current location, and thus forcing a lock on the phone? Not sure..
Click to expand...
Click to collapse
You would think but I have my watch connected to it as well both wearos or fitbit sense and same issue with smart lock, so not just location limited.
Noticed the same problem here. My old device I just used the rear finger print scanner, it was instant on and in, with the Pixel 6 Pro the finger print reader is neither in the best place or the quickest, and if you are in a dark place and don't aim properly, its a blinding light! So I thought at least at home I can use smark unlock. Worked fine yesterday, today it wouldn't stay unlocked. All settings appeared okay, my address was shown as a trusted place, I loaded maps so it get my location (it was already showing me at home anyway), but just not working.
I then removed my trusted place, readded, exactly the same address from the pinpoint on the map was shown, and it is working again.
I took the 4 hours to mean that after 4 hours you would need to sign in again once, then you get another 4 hours of smart unlock.
Just a buggy piece of Google software I guess.
Honestly I don't think I've ever had Smart Lock that really worked on ANY of my android phone. It works when it wants to.
Smart Lock has been janky since original pixel and the nexii before that.
I posted this question in the A13 Beta 4 thread but didn't got any feedback, so post it as a separate question to see if someone can help.
I switch to A13 since beta 2 and just updated to beta 4, everything seems run smoothly. However, I just found out that my "Google Assistant" lost the "beep" sound! What it means is that if I say "OK, Google" or "Hey, Google", I can carry out to give the command or instruction as I want but I am losing the "Ting" sound of the reaction once I say "OK Goolge" or "Hey Google". It's not really a big deal but just gave me a funny feeling as I would have to look at the phone screen to see if Google Assistant really working. All I can say is that I don't know when this is started as I didn't use Google Assistant for quite a long time, but it is definitely working when my P6P was on A12.
Can't someone confirm if this is just me or if there is a setting I can get this "beep" sound to come back. I play around with the phone for a couple hours and couldn't figure out any setting in "Google" app, "Assistant" app and system sound to have this be related.
acwcanada said:
I posted this question in the A13 Beta 4 thread but didn't got any feedback, so post it as a separate question to see if someone can help.
I switch to A13 since beta 2 and just updated to beta 4, everything seems run smoothly. However, I just found out that my "Google Assistant" lost the "beep" sound! What it means is that if I say "OK, Google" or "Hey, Google", I can carry out to give the command or instruction as I want but I am losing the "Ting" sound of the reaction once I say "OK Goolge" or "Hey Google". It's not really a big deal but just gave me a funny feeling as I would have to look at the phone screen to see if Google Assistant really working. All I can say is that I don't know when this is started as I didn't use Google Assistant for quite a long time, but it is definitely working when my P6P was on A12.
Can't someone confirm if this is just me or if there is a setting I can get this "beep" sound to come back. I play around with the phone for a couple hours and couldn't figure out any setting in "Google" app, "Assistant" app and system sound to have this be related.
Click to expand...
Click to collapse
You have to turn on an accessibility option. Once I remember where it's at I will post again
thethruth said:
You have to turn on an accessibility option. Once I remember where it's at I will post again
Click to expand...
Click to collapse
And then you turn on switch access but it doesn't make the system run as smoothly for some reason. I want the beep as well but I had to eventually turn the option off. Try it out. Don't see if you like it
thethruth said:
And then you turn on switch access but it doesn't make the system run as smoothly for some reason. I want the beep as well but I had to eventually turn the option off. Try it out. Don't see if you like it
Click to expand...
Click to collapse
Thanks for pointing me to this. Like you said, I don't like it at all! I even not giving enough time to see if it would affect how the system runs but getting an accessibility slider when volume button is pressed when "Switch Access" is turned on already make me hate it. I couldn't find a thing how this accessibility slider is doing but definitely don't want it to appear whenever I press the volume button.
I never turn on anything in Accessibility menu, always leave it as default. This seems to be a A13 thing as I remember that the Assistant has the beep when I was on A12. Anyway, I will try to make myself get used to this behavior.