Related
Is anyone here experiencing this bug:
http://code.google.com/p/android/issues/detail?id=23197
The lag happens BEFORE the face recognition takes place. It's clear the lag does not come from the face recognition. Instead it's probably coming from the time it takes for the camera to launch/activate. Now, the lag is not serious, but it did tend to get worse. However, I am very very sure that when I receive the Galaxy Nexus the first day, the lag wasn't there. The camera was ready to recognize my face almost instantly. I have 4 Galaxy Nexus in my family, and I had to set up the phone 4 times, so I am pretty sure that Face Unlock starts up really quick the first day.
Honestly I think it's just Android itself. The longer you own an Android phone and the more you use it, the laggier it gets :/ .
Game4set said:
Honestly I think it's just Android itself. The longer you own an Android phone and the more you use it, the laggier it gets :/ .
Click to expand...
Click to collapse
Well, this is applicable to almost every OS. It happened to my Mac, my Windows 7 PC, and a quick search in Google reveals many iPhone users complaining about the same thing (of course, they won't admit it publicly -- but they can't hide it in a Mac oriented forums ;-))
But it doesn't feel right in this case because the lag actually seems coming from the fact that the camera or the Face Unlock app wasn't in the memory ready to be used. If this is in fact the case, there are things Google can do to improve the experience.
On a side note, if I recalled correctly, I used to see Face Unlock in my running app list, but I no longer see it now. I wonder if this has anything to do with this bug.
Yes! I've been noticing this. And it is definitely only since I got the 4.0.2 update a couple of days ago. Before that it was near instant, now it lags
Although I have to admit, it recognised my face so poorly with 4.0.1 that I had to turn it off. Now with improved face matching I can use it all the time, I just hope they fix the lag.
Maybe someone running a custom rom on 4.0.3 can confirm whether they have the lag too.
case0 said:
Yes! I've been noticing this. And it is definitely only since I got the 4.0.2 update a couple of days ago. Before that it was near instant, now it lags
Although I have to admit, it recognised my face so poorly with 4.0.1 that I had to turn it off. Now with improved face matching I can use it all the time, I just hope they fix the lag.
Maybe someone running a custom rom on 4.0.3 can confirm whether they have the lag too.
Click to expand...
Click to collapse
Face Unlock rarely has problem recognizing my face. When Face Unlock fails to work, it's almost always due to the lighting -- I could barely see my face from the camera's preview myself at those time, how could I expect the phone to recognize me? Generally speaking, if my face is right around where the dotted face outline is, and there's is enough light for me to see my face in the camera preview, Face Unlock always work for me.
I was also suspecting the 4.0.1 update was the cause of problem. I just didn't have the time to confirm it.
I get this too. I wonder if its that it has more pictures to use to analyze in 4.0.2 vs 4.0.1. It annoys me that it takes just a little too long.
---------- Post added at 11:34 PM ---------- Previous post was at 11:18 PM ----------
Does anyone with a 4.03 rom have lag on face unlock?
I bet it happens over time because we start to load apps and android naturally bumps the camera out of memory and so each time we go to screen unlock it has to load it up and start the camera which takes a bit of time.
spinkick said:
I get this too. I wonder if its that it has more pictures to use to analyze in 4.0.2 vs 4.0.1. It annoys me that it takes just a little too long.
---------- Post added at 11:34 PM ---------- Previous post was at 11:18 PM ----------
Does anyone with a 4.03 rom have lag on face unlock?
I bet it happens over time because we start to load apps and android naturally bumps the camera out of memory and so each time we go to screen unlock it has to load it up and start the camera which takes a bit of time.
Click to expand...
Click to collapse
I don't think it has to do with more pictures to analyze. I've tried clearing all the data and start from scratch, but it did not fix the problem. Also, the actual facial recognition work really quick -- if having more picture is affecting it, it will be because there're more data needed to be read to initialize the app. However, I see no reason why the app needs to load all the data before it even starts to recognize the face.
New Gnex owner here (of a grand total of 3 days). Rooted my phone my first day, flashed milestone 4, and all is good--except the face unlock screen seems to take 1-3 seconds to boot up the camera.
I don't recall it being an issue on day 1, but it is definitely now noticeable. I love the feature and would be immensely satisfied if the delay could be minimized...does anyone NOT have the lag?
givonion said:
New Gnex owner here (of a grand total of 3 days). Rooted my phone my first day, flashed milestone 4, and all is good--except the face unlock screen seems to take 1-3 seconds to boot up the camera.
I don't recall it being an issue on day 1, but it is definitely now noticeable. I love the feature and would be immensely satisfied if the delay could be minimized...does anyone NOT have the lag?
Click to expand...
Click to collapse
Yup, same here. This feature is really useful for a phone as big as the GNex -- it's not that easy to swipe unlock with just one hand. I am using 4.04 and the bug still hasn't been fixed. I have tried all kind of tweaks, and none of them work.
I suggest you to comment on the official issue tracker and "star" it. The more people complain about it, the higher the chance it gets fixed soon.
I've only started using Face Unlock for a few days on 4.0.2 and only then to impress girls. I haven't experienced any lag so far. Face Unlock takes some time to set up for me though, and I have to tilt the phone in a unnatural angle to allow the camera to see my whole face.
Same issue here, after yesterday's update to 4.0.4 the camera literally never starts. Just a blank screen with clock and no back software button. I have to press emergency dial then back to get to the pattern lock. Happens 1 in 5 times I try to unlock.
I updated my Galaxy Nexus with Jelly Bean and Google seems to put a "fix" to this bug. Before you celebrate, here's the bad news -- no, I don't think they actually "fix" the underlying problem. In Jelly Bean, when you wake your phone up to use Face Unlock, instead of seeing a black screen, there will be an "animation" that gradually transits from a black screen to the camera. Amazingly, that simple trick seems to make the lag much less annoying, to the point that I don't feel there's a lag at all.
Game4set said:
Honestly I think it's just Android itself. The longer you own an Android phone and the more you use it, the laggier it gets :/ .
Click to expand...
Click to collapse
but it will never lag after a reboot. *the first 20 mins*
zeke1988 said:
but it will never lag after a reboot. *the first 20 mins*
Click to expand...
Click to collapse
I don't know about you, but I still saw the lag sometimes after I rebooted (with ICS.)
Fix ....Ok I think I've done it but need further testing ...
Ok I think I've done it but need further testing ...
Only possible on rooted devices ..
Go to folder
/data/data/com.android.faceunlock/shared_prefs/
in your root enabled file browser (I used es file explorer)
Open the file inside
Edit delay number to 1
Save file
Then change permissions to read only by all
And ownership to root
Go 1 level up and do the same with the shared_prefs folder (perm and owner)
And again 1 up and same settings to the com.android.faceunlock
Come back here and report if it improved
Not sure if all the permissions must be like that but I went safe on it since file got replaced first few times I tried
Please do.come back here to report if it worked for you too
My delay was 1730 after changing to 1 it worked like charm once but then it changed to ~700(file got updated again) then I've changed the settings of files and folders to present override and now I did not experience the lag yet
Let me know if you need more info or more detailed instructions 0,O
Also I feel I should mention ive done it on moto g 1st gen running 4.4.4
And that minimum time for it to open is same as time it takes to swap from back to front camera in your stock camera app plus time it takes to detect light conditions and in dark places it takes longer to do that
OK, so now that I have lollipop, I have noticed a few things are broken and I am wondering what other problems others are having and what we can collectively do to try and fix them.
If I tilt and say "OK Google" and "Show me my heartrate" I get a momentary black screen and then back to the watch face. Happens with both Fit and the Moto app
I noticed it happens more when I have a partial notification card showing. If I clear the notification and turn the screen back on it will usually work right.
Also, downloaded the update while on the charger then ran the update with 100% battery, now three hours later I'm down to 34%. Yikes. I've had the watch for only a couple days so I'll give it more time to settle in.
David
FWIW whenever i run updates i lose an easy 15%+. all of that on-screen time and processing shows the inefficiencies of the processor. i generally try to re-charge it after any update.
additionally its been reported several times to perform a factory reset on the watch after any update. i haven't performed one yet myself, but by battery life has been on-par with before.
lollipop
Do you have lollipop on your phone? I notice that when i got lollipop on my 360 the battery went down pretty quick! I had the 360 connected with my M7 on kitkat! Now i have my 360 connected with my Nexus 6 and its working ok!
DaveTN said:
OK, so now that I have lollipop, I have noticed a few things are broken and I am wondering what other problems others are having and what we can collectively do to try and fix them.
If I tilt and say "OK Google" and "Show me my heartrate" I get a momentary black screen and then back to the watch face. Happens with both Fit and the Moto app
I noticed it happens more when I have a partial notification card showing. If I clear the notification and turn the screen back on it will usually work right.
Also, downloaded the update while on the charger then ran the update with 100% battery, now three hours later I'm down to 34%. Yikes. I've had the watch for only a couple days so I'll give it more time to settle in.
David
Click to expand...
Click to collapse
Anyone have problems with the unlock your phone feature using a different launcher like nova. I have mine paired to my nexus 6 and it works great on Google launcher but only about a third of the time on nova, thanks
Sent from my Nexus 6 using Tapatalk
*Hello everyone! I really can't wait to get my hands on a giulery Huawei Watch but in my country it will be availeble only from November. So i start looking on ebay and Amazon. I found one review that realy concerns me on Amazone. And i quote:
" The Huawei Watch has a major software issue. When the watchface goes in to ambient mode, it often freezes, and the only way to unfreeze it is through a reboot. This happens to me at least 5-6 times each day. When a freeze occurs, the watch hands are stuck on the hour and minute that were showing at the time of the freeze. You can press the crown and the screen brightens, but it doesn't leave ambient mode, and it doesn't return to the correct time. I did a factory reset on mine after one day of use to see if this might fix the problem, but nothing changed. I called Huawei tech support, and this is a known issue. They told me a software fix would be rolled out "soon". I thought I could tolerate it until they got it fixed, but this is driving me crazy. Last night, it locked up three times inside of a 30 minute period. I find myself clicking the crown frequently thorughout the day, not because I want to know what time it is or because I want to use an advanced feature, but only to see if the watch has frozen again. What good is a watch that won't tell time?"
So, please advice if enyone has this issue. Thanks and sorry for my english.
Sent from my SM-N910F using Tapatalk
I have had the Huawei watch for over a week and have never experienced this at all!
Everything works perfect, and I have not had any issues whatsoever.
Here the same... more than a week using the Huawei Watch and I did not encountered any problem.
I haven't had this problem either. But, I did have to return mine because of another problem. I would not buy through Ebay, stick with an retailer like BB or Amazon so you can exchange it easily if there is a problem.
--------------------
smentoma said:
*Hello everyone! I really can't wait to get my hands on a giulery Huawei Watch but in my country it will be availeble only from November. So i start looking on ebay and Amazon. I found one review that realy concerns me on Amazone. And i quote:
" The Huawei Watch has a major software issue. When the watchface goes in to ambient mode, it often freezes, and the only way to unfreeze it is through a reboot. This happens to me at least 5-6 times each day. When a freeze occurs, the watch hands are stuck on the hour and minute that were showing at the time of the freeze. You can press the crown and the screen brightens, but it doesn't leave ambient mode, and it doesn't return to the correct time. I did a factory reset on mine after one day of use to see if this might fix the problem, but nothing changed. I called Huawei tech support, and this is a known issue. They told me a software fix would be rolled out "soon". I thought I could tolerate it until they got it fixed, but this is driving me crazy. Last night, it locked up three times inside of a 30 minute period. I find myself clicking the crown frequently thorughout the day, not because I want to know what time it is or because I want to use an advanced feature, but only to see if the watch has frozen again. What good is a watch that won't tell time?"
So, please advice if enyone has this issue. Thanks and sorry for my english.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
No issues like that here, isolated incident
No such issues here after 5 days of use here as well.
Only 'issue' experienced: Lost connection to phone once and wouldn't reconnect. rebooted both and worked instantly.
Here's the deal.
smentoma said:
*Hello everyone! I really can't wait to get my hands on a giulery Huawei Watch but in my country it will be availeble only from November. So i start looking on ebay and Amazon. I found one review that realy concerns me on Amazone. And i quote:
" The Huawei Watch has a major software issue. When the watchface goes in to ambient mode, it often freezes, and the only way to unfreeze it is through a reboot. This happens to me at least 5-6 times each day. When a freeze occurs, the watch hands are stuck on the hour and minute that were showing at the time of the freeze. You can press the crown and the screen brightens, but it doesn't leave ambient mode, and it doesn't return to the correct time. I did a factory reset on mine after one day of use to see if this might fix the problem, but nothing changed. I called Huawei tech support, and this is a known issue. They told me a software fix would be rolled out "soon". I thought I could tolerate it until they got it fixed, but this is driving me crazy. Last night, it locked up three times inside of a 30 minute period. I find myself clicking the crown frequently thorughout the day, not because I want to know what time it is or because I want to use an advanced feature, but only to see if the watch has frozen again. What good is a watch that won't tell time?"
So, please advice if enyone has this issue. Thanks and sorry for my english.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
If you use certain watchmaker watch faces, since they currently don't support this watch, I have noticed that effect on certain watch faces in ambient mode. Never with the one's the watch shipped with. I do not know if any other watches have round amoled displays so you have to guess which one to use with the watch, I chose first Moto and then a LG square face, both would freeze in ambient mode, so for the meantime I have stopped using watchmaker until the developer updates it to support our watch. To bad, I paid for the full version of the app, before I discovered this. But with any of the ones that come with the watch, never will happen.
smentoma said:
*Hello everyone! I really can't wait to get my hands on a giulery Huawei Watch but in my country it will be availeble only from November. So i start looking on ebay and Amazon. I found one review that realy concerns me on Amazone. And i quote:
" The Huawei Watch has a major software issue. When the watchface goes in to ambient mode, it often freezes, and the only way to unfreeze it is through a reboot. This happens to me at least 5-6 times each day. When a freeze occurs, the watch hands are stuck on the hour and minute that were showing at the time of the freeze. You can press the crown and the screen brightens, but it doesn't leave ambient mode, and it doesn't return to the correct time. I did a factory reset on mine after one day of use to see if this might fix the problem, but nothing changed. I called Huawei tech support, and this is a known issue. They told me a software fix would be rolled out "soon". I thought I could tolerate it until they got it fixed, but this is driving me crazy. Last night, it locked up three times inside of a 30 minute period. I find myself clicking the crown frequently thorughout the day, not because I want to know what time it is or because I want to use an advanced feature, but only to see if the watch has frozen again. What good is a watch that won't tell time?"
So, please advice if enyone has this issue. Thanks and sorry for my english.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
I have absolutely same issue. Just bought Huawei Watch and immediately first day it froze in ambient mode. I did restart/factory reset, nothing helped, it happens every day, sometimes every hour. The problem is the ambient mode itself. I figured out how you can unfreeze it if this occurs even without restart: on your phone go in Android wear app and in Settings turn on/off function Always-on-screen. After this it works again, but this does not fix that issue that it freezes and the time freezes as well, thus the watch is useless at this moment. Now I use watch without ambient mode and it seems the watch works pretty fine. Please let me know, once someone knows the root case and how to permanently fix this.
There are a few other people complaining about this too in the various forums. I returned my first watch because of this.
In the meantime i bought the watch from Usa. I install many apps and i use watchmaker premium with a superb watch face that i modified and name it huawei watch 2015. I cant say if is freezing in dim mode but i have some ocasional problem with certan app 3 part. Android wear is a great system for notification but is crushing a lot. I can use my watch at full capacity but i have to restart it like 2 time a day to function well. I like this weatch to much to mind that. Install task manager for wear and restart the watch one time and you shoud be fine.
Sent from my SM-N910F using Tapatalk
My huawei watch reboot itself 2-3 times every hour when using WatchMaker Premium Watch Face and the wake gesture works only 1 time when activated
The OP post fault was locking up (had this issue too on my first watch)
This post is not related but I would say uninstall WatchMaker Premium Watch Face, use a stock watch face.
If the problem disappears contact the WatchMaker vendor.
A faulty application has nothing to do with the watch.
Only had 1 reboot in a month. I consider that more than acceptable!
Good luck to you!
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Make sure 'card previews' turned on from the android wear app, other wise your experience with the faces sounds buggy! A factory reset would help on that.
Factory reset doesnt work, this also happens to me since the update, looks like this is a firmware problem.
Damnit, I wish I didn't update.
Battery is also noticeably worse.
airjordan223 said:
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Click to expand...
Click to collapse
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
antknee2016 said:
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
Click to expand...
Click to collapse
Can you found a way to fix it?
Enviado desde mi SM-N920I mediante Tapatalk
The first issue is because the watch now comes on in ambient mode first. Even if you don't use ambient mode. It sucks. Luckily i use Watchmaker for my watch face so I went in and made all the parts (hands date etc...) to be visible in ambient mode.
I have noticed that if I wait a couple of seconds the notification does appear on my watch screen but it is after the vibrate, not immediate. I thought it wasn't showing up at first too. Still, I wish it was quicker as I look right away.
Sent from my SHIELD Tablet using Tapatalk
I went back to using Facer for my watchface and the delay is gone.
Also did they completely remove the restart option? Now it's just power off, and then press and hold the side button.
I'm experiencing both issues as you do on 6.0.1.
Also yes, reboot option is gone from update.
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Sent from my SHIELD Tablet using Tapatalk
frenziedfemale said:
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Click to expand...
Click to collapse
Reboot is not reset...
I've also noticed that theater mode does not work after the mm update (unrooted, ota). I usually set it to theater mode at night to avoid burn in and just because I don't want it on all night. Now, it looks like it's blacked out, but when I wake up, the charging screen is lit up. Anyone else getting this?
I have the exact same issue after the update. Theater mode will not keep the display off if the watch is being charged. Off the charger, it works as expected. Quite an annoying bug.
If I turn ON the theatre mod with double press the power button before I put the clock on the charging dock, after that screen continue charge with screen off.
For me it's work.
Can anyone try it?
Sent from my D6503 using XDA Free mobile app
Just tried that - doesn't work for me. Screen turns off but once I put it on the charger, it comes back on after a few seconds. I'm watching it and it's still on a few minutes later.
Same here. Screen always turns back on
I'm getting the first bug the OP mentioned havn't noticed the second one though.
However the first bug is annoying enough, hopefully there'll be a quick patch.
Little patience, update to Marshmallow is great.
Here's what I mean with screen off when charge:
So in the morning until you take it out of the dock and go to work.
Sent from my D6503 using XDA Free mobile app
still on 5.0.1
man i just boughjt it 2 days ago and battery sucks,now i am trying to update cause i heard batter improved,but i cant ,watch start download but take too long and then show me a message charger to update blah blah but phone is charger is over 90 percent i have reset phone and uninstalled app many times this is ridiculous now i know why motorola was giving away this pos when yopu buy the 64gb moto x pure edition arrrrgggg
Srandista said:
Reboot is not reset...
Click to expand...
Click to collapse
Sorry I read wrong...but wouldn't you just use the power off option and then turn back on to reboot?
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.