Hello everyone,
It has been a while since I ventured through this forum, but it seems that y'all may be my only hope.
I've been suffering through this glitch/stutter that, when scrolling, the phone registers my finger as taps everywhere my finger slides. All I simply need to do it remove my finger from the phone and I can continue scrolling like normal. It is super annoying and I cannot find out what causes it, it just seems random. It never happened on any of my Nexus phones in the past.
Now, here's a list of things I've tried in order to fix it:
- Safe mode
- Factory Reset (Restore from Google account)
- Factory Reset (New Device option)
- RMA'd through Google support and received a new pixel and the problem persists (even after going through the steps above on the new device)
Here is a short video of the glitch while it is happening.
https://goo.gl/photos/GysQXd82MexVkk836
(Hopefully that link works)
Note: the glitch will not stop until I take my finger off the phone, you can tell when it is happening when I scroll over the share button and it registers as a tap.
If you guys have any suggestions, I'm ready to try anything at this point. I don't want to go through Google support because I know they'll send me yet another Pixel (I've already talked to them again and that was their solution, I told them I'll try a few more things) and I feel like that is a waste. I'm almost 100% positive that this is a software glitch, not hardware.
Thanks!
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Jaxidian said:
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Click to expand...
Click to collapse
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Skillfulshoe said:
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Click to expand...
Click to collapse
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Jaxidian said:
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Click to expand...
Click to collapse
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
I'm not sure if this is caused by a bad touchscreen sensor because I've had the problem on two separate Pixel phones so far. Or maybe I just got super unlucky with two faulty phones.
I don't think my fingers are too dry. If all else fails, I'll try moisturizing them I guess. I've never had this problem on all my other phones though, but I guess you never know.
Thanks for the help.
Skillfulshoe said:
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
Click to expand...
Click to collapse
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Jaxidian said:
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
Click to expand...
Click to collapse
Yeah I totally understand what you're saying. I just have gotten frustrated with this. I know it isn't a big deal honestly.
gadgetgaz said:
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Click to expand...
Click to collapse
Yeah that could be what causes it. Maybe it is just the way we are scrolling and how Google has calibrated the screen touch sensors.
Possible Fix
So I went into accessibility settings and changed the duration you need to hold your finger down to do a long press to medium (from the default as short). It seems that may have fixed it. I haven't experienced the glitch since I've done that change.
Here's to hoping that did indeed fix the issue.
Thanks everyone.
Related
HTC Sensation: Possible solution of "phone doesn't sleep" and "power button" problem
Hi every body,
I was getting irritated and extremely fed up of basically two problems of my htc sensation:
1- The phone didn't automatically turn the screen off. The screen would remain ON and wouldn't automatically lock itself. For example, i use the phone and then i will place it at a side expecting that first screen will be dimmed and then phone will automatically lock itself. It wasn't happening since a very long time (I don't remember the beginning of problem), even when screen timeout setting was enabled. I also observed that if at one time i set the brightness level of display to be automatic, next time i check it and brightness level was always set to be at maximum level.
2- When i pressed the power button to lock the phone, the phone often doesn't go dark. It went dark for a second and then became ON again. I had to press it a number of times until it goes dark. Similarly when i wanted to unlock the phone, i had to press the power button multiple number of times, until it gets unlocked.
Basically i was trying to solve the 1st problem. I went into settings -> applications -> manage application. I checked for each installed application whether it has following in the permissions:
System tools: prevent phone from sleeping
Following applications had above mentioned permission, so i removed them:
xda
ebay
mobile voip
daily motion
sports tracker
Calorie Counter - MyFitnessPal
imdb
Photo Editor
speedtest.net
whatsapp
yahoo messenger
Surprisingly after removing those apps, both issues 1 & 2 were totally gone. The phone was automatically locking it self (it still is). So for me problem number 1 is totally gone now.
However, regarding second problem, i tested it like 100 times locking and unlocking the screen by pressing power button. The behavior was absolutely normal. Then i checked the brightness level of phone, it was set to maximum, i set it to automatic. As soon as i set the brightness level to be automatic, the 2nd problem somehow reappeared.
Now if i set the brightness level manually, the 2nd issue doesnt reappear, but when i set the brightness level to be automatic, power button issues reappears.
Sorry for such a long post but I hope may be this post helps someone, also i would like to ask the experts the justification of such behavior of phone.
I am using stock rom and android version 2.3.4, sense version 3.0 and software number 1.50.206.1
This definitely needs a bump!
I was thinking of possible solutions as well, but this one makes sense. Maybe it is a flaw in how that permission is handled? I don't know how to program, but if any of you clever rom hackers are around, maybe you can try tweaking this? I was thinking that it was maybe something to do with the hardware button itself, sending off multiple signals to the phone telling it to lock and unlock right after due to the shoddy power button design.
My main issue with the fix in the original post is that I use a lot of apps that require this permission, and apps are kinda what define how useful your phone is (aside from making phone calls, that is). If there was a way to fix this issue by either tweaking the "prevent phone from sleeping" permission, or maybe just trying to add an input delay that doesn't register any power button presses until half a second has passed or something.
Like I said, I don't know what is possible to tweak with android since I don't know how to program so I might just be talking out of my butt, however, I do like this phone, it just has this one major power button flaw that really annoys me!
#2 doesn't occur in ICS Roms. I'm always on auto brightness.
Some ROMS added some apps may let your phone awake automatically when you close the screen,so it is the right way to move some apps. Using ARHD ICS and Insection ICS ROMS ,#1#2problems never happend.
Basically i would like to stick to original stock rom. I know i can avoid these problems if i use custom roms.
@Tekuno
Let me tell you, i didn't delete all of those apps which were using that permission "prevent system from sleeping". I only deleted those which i mentioned in my 1st post. Among those, i installed "yahoo messenger" again and 1st problem started happening again. I removed that app, problem gone. For me it's the case of hit and trial. I can't definitely point out one specific app which cause the problems.
I think there is really a flaw in the way this permission is handled by operating system of the phone.
I would also like to keep with the stock rom if possible. I figured it would only be a few apps that would be causing the lock screen issues, I am currently too lazy to go through all of the apps and figure out which ones are causing it.
I'll wait patiently for the ICS and Sense 3.6 update and see if that helps.
i have both problems too. About no 2, i always tot it happens after using the stock camera app which forces the brightness to go maximum and sometimes after exiting, there is some bug that doesnt return setting to automatic. Just a hunch but not sure :s
Do you have "Extended quick settings" installed ? and on a custom ROM, if so then i guess you need to check the "Screen On" option in the extended quick settings dropdown window.
You must have accidentally pressed it and activated it instead.
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance
crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.
Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.
Hey guys.
Stumbled upon this on YouTube. Bought the app and I can confirm that it works.
This is the app: https://play.google.com/store/apps/details?id=com.used.aoe
Here's the video I found on YouTube:
I managed to get it setup just the way I like. The guy in the video is a bit hard to understand but the video is good enough to get you started.
If your looking for a deeper dive into the optimal configuration process try this thread
https://forum.xda-developers.com/s10-plus/how-to/workaround-missing-notification-led-edge-t3919286
Enjoy!
thanks a lot =)
But is it posible to set different colors for different apps?
for example
green = whatsapp
blue = facebook ....
UPDATE: there is an option .... "when a notification comes" there you got the option "select enabled aps ots color and time" the blue button =)
neigo said:
thanks a lot =)
But is it posible to set different colors for different apps?
for example
green = whatsapp
blue = facebook ....
Click to expand...
Click to collapse
Yes
Thanks for the effort.
Just tried it, buggy as hell and didn't play nice with my lock screen. Also every 30 seconds the screen would flicker.
I'll keep an eye on it and maybe try again after more refinement.
bomp306 said:
Just tried it, buggy as hell and didn't play nice with my lock screen. Also every 30 seconds the screen would flicker.
I'll keep an eye on it and maybe try again after more refinement.
Click to expand...
Click to collapse
I had nothing but issues out of the app. Notifications wouldn't notify, the lock screen turned on and off randomly, there were no edge lighting effects no matter what I adjusted. I even tried to use the camera cutout, it again did not work.
This is a VERY bloated app, containing a LOT of features and options that frankly, are of no use to me or of no interest to me. I want an app that it's ONLY purpose is to alert me when I get messages, calls, and email. one that does not have so much bloat so that the developer can focus on the feature that is most sought after at the moment.
Just my two cents.
tl;dr App is junk, has too much junk, we need a debloated app.
It's a start...
b3y0ndd34th said:
I had nothing but issues out of the app. Notifications wouldn't notify, the lock screen turned on and off randomly, there were no edge lighting effects no matter what I adjusted. I even tried to use the camera cutout, it again did not work.
This is a VERY bloated app, containing a LOT of features and options that frankly, are of no use to me or of no interest to me. I want an app that it's ONLY purpose is to alert me when I get messages, calls, and email. one that does not have so much bloat so that the developer can focus on the feature that is most sought after at the moment.
Just my two cents.
tl;dr App is junk, has too much junk, we need a debloated app.
Click to expand...
Click to collapse
Come on! This app might not be right for you, but the developer should at least be given some credit/thanks for the effort taken to solve a problem, for which several users are seeking a not really forthcoming solution from Samsung. You "want an app...", but the developer created something and shared it. Granted, the app has far too many options and choices, but I was able to get it working to my satisfaction. Let's be thankful first .
- Paul
cmexec said:
Come on! This app might not be right for you, but the developer should at least be given some credit/thanks for the effort taken to solve a problem, for which several users are seeking a not really forthcoming solution from Samsung. You "want an app...", but the developer created something and shared it. Granted, the app has far too many options and choices, but I was able to get it working to my satisfaction. Let's be thankful first .
- Paul
Click to expand...
Click to collapse
Okay, okay, okay. I may have been a little harsh. I didn't mean to demean to developer. I am very thankful they have taken the time to create this app out of the kindness of their heart, as well as make the app free. I appreciate the work they have done and I would even donate if I could get the app to work; however it's not very user friendly tough, and in my opinion, could use a lot of work on many different aspects.
My main issue with the app is that it does not work as intended. I have tried using the youtube video settings, playing with options, etc.
I download and re-install this app about 5 times a day in hopes that MAYBE one time I can get it to function as intended. But I do not get any kind of Edge lighting or Notch cutout alert when I get messages, and that is the sole purpose of my attempts with this app, if I could find something similar or something that better served this purpose I would use it instead.
Sometimes, while using the apps lock screen, it will display the little icon and the message but then it goes away, and doesn't re-alert like it is suppose to, and the light affects do not appear. I have tried leaving it as the stock color and using a custom color. I have tried using the app lock screen, I have tried using the settings within the app to let it manipulate the wallpaper and lock screen, tried it with an image and also just a black background. I never even delved into setting different colors for apps, I can't get the dang notifications to work!
end rant
Do you have edge light on? Worked for me first try. I am not saying its 100% but for free and for now to wait to see if Samsung might give us we want I will leave it on my phone.
hello,
with this app is there a setup to leave the screen off when a notification comes in and only the cam ring turns on then?
thanks
m8980 said:
hello,
with this app is there a setup to leave the screen off when a notification comes in and only the cam ring turns on then?
thanks
Click to expand...
Click to collapse
Yes
it is working a bit strange for me as well. I've managed to get it to ALMOST work how I want, but I can't figure out why it will do random things
-- for a while it was turning on my screen when the edge lighting came on, which was pointless. I changed a lot of settings in troubleshooting, but I'm not sure what I did to fix it
-- also, it does notify every 30 seconds even though I have no new notifications. that one I haven't figured out yet
It does work as advertised though, despite the bugs I can't fix. It will either light up my edge lighting or the notch around the camera (which I prefer). so props to the dev for figuring that part out and here's to hoping the rest of the bugs get worked on the S10 (and my S10+). it seems to be working for other devices (I originally found it here for the oneplus)
dragonOL2 said:
it is working a bit strange for me as well. I've managed to get it to ALMOST work how I want, but I can't figure out why it will do random things
-- for a while it was turning on my screen when the edge lighting came on, which was pointless. I changed a lot of settings in troubleshooting, but I'm not sure what I did to fix it
-- also, it does notify every 30 seconds even though I have no new notifications. that one I haven't figured out yet
It does work as advertised though, despite the bugs I can't fix. It will either light up my edge lighting or the notch around the camera (which I prefer). so props to the dev for figuring that part out and here's to hoping the rest of the bugs get worked on the S10 (and my S10+). it seems to be working for other devices (I originally found it here for the oneplus)
Click to expand...
Click to collapse
you need to disable edge lighting in setting to use this app or else it will conflict since this app does wake up the screen while edge lighting is not.
if u enable both that mean this app waking up the screen, then edge lighting will also showing (coz edge lighting while screen is on is applied). you will have both notification then
psy07 said:
you need to disable edge lighting in setting to use this app or else it will conflict since this app does wake up the screen while edge lighting is not.
if u enable both that mean this app waking up the screen, then edge lighting will also showing (coz edge lighting while screen is on is applied). you will have both notification then
Click to expand...
Click to collapse
thanks! Not sure if it was changing that setting that helped, or their recent update I got yesterday, but the weird behavior has seemed to subside for a bit... I'll give it a few more days of testing to see if I can find anything else weird, but so far so good. I might also try swapping out the default color with individual colors for each app soon. Glad the dev seems to be open and receptive to feedback and willing to keep his app updated to fix various bugs found
The Reminder Notification Option
Has anyone successfully gotten the reminder option to work? When used, this is supposed to repeat the notification lighting for a brief period, if a notification had been unanswered for a period of time (30 or 60 seconds - I think). However, I could not get that to work - or at least replay the lighting. incidentally, I notice that Sakitech did not "fully" demo this feature in his Youtube tutorial. He mentioned it (at about 6:08), but did not show it working, I suspect (only speculating...) that he edited it out of the video because it does not work properly.
If anyone has the right settings for **** please share.
DetoxVenom said:
If anyone has the right settings for **** please share.
Click to expand...
Click to collapse
Did you whatch the video in the OP? It's sorta thorough.
Sent from my SM-G975W using XDA Labs
View attachment 4734017
cmexec said:
Has anyone successfully gotten the reminder option to work? When used, this is supposed to repeat the notification lighting for a brief period, if a notification had been unanswered for a period of time (30 or 60 seconds - I think). However, I could not get that to work - or at least replay the lighting. incidentally, I notice that Sakitech did not "fully" demo this feature in his Youtube tutorial. He mentioned it (at about 6:08), but did not show it working, I suspect (only speculating...) that he edited it out of the video because it does not work properly.
Click to expand...
Click to collapse
Use these settings and save.
rogerandgina said:
View attachment 4734017
Use these settings and save.
Click to expand...
Click to collapse
Thanks! The only setting I have differently is "double top to close" instead of "swipe up to close". Otherwise, I have been using these exact settings . As usual, at the moment that the screen should display the reminder, all that happens is the phone vibrates, but the light is not illuminated or display any visible interaction with the AOE lighting app.
cmexec said:
Thanks! The only setting I have differently is "double top to close" instead of "swipe up to close". Otherwise, I have been using these exact settings . As usual, at the moment that the screen should display the reminder, all that happens is the phone vibrates, but the light is not illuminated or display any visible interaction with the AOE lighting app.
Click to expand...
Click to collapse
Yeah, I see what you mean. My app as well will not work properly. I don't know what is going on? I have reached out to the developer and still not able to resolve the issues. The app starts out good but then goes rogue after awhile. I thought it was good lock messing it up but I was wrong. I give up for now.
cmexec said:
Thanks! The only setting I have differently is "double top to close" instead of "swipe up to close". Otherwise, I have been using these exact settings . As usual, at the moment that the screen should display the reminder, all that happens is the phone vibrates, but the light is not illuminated or display any visible interaction with the AOE lighting app.
Click to expand...
Click to collapse
Try turning off the "Manually only when I want it, I open the app". Also change the "When a notification comes" "And screen is off" to "Always off or on". Be sure you have turned off the Edge lighting in your phone settings.
What I was finding is when a notification would come in, it would light up the screen for a second and this would cause the app not to show the notification because I set it to "And screen is off" condition causing several notifications, if not all, to make the app not work. Once I changed to it to either/or, it has been working great for me. Hope this helps
Maybe it's a common issue but I haven't found any info when searching about it.
I have a P11 Pro, and since I got it, I have always been having the same issue with the tablet waking up on its own quite often, randomly, or even sometime refusing to go back to sleep.
I disabled any setting that might waking it up (tap to wake, move to wake...), and disabled several apps, but it changes nothing.
It's especially annoying since when I don't use a screen lock, with the 5 minutes stay on time I set, it keeps waking and empty the battery quite fast.
Using a screen lock reduce the issue as the tablet goes back to sleep quickly, but still doesn't solve the problem. And I don't want to use screen lock when I use the tablet at home.
Does any you know that issue, or how to fix it?
Thanks in advance!
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
hashtowent said:
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
Click to expand...
Click to collapse
Nothing connected.
Yeah the lid has a sensor, but it does it even when I remove the cover completely or when I leave it closed and not moving.
Yes I did several factory reset, update of the firmware, and yes I'm on the latest one.
As far I can understand, a process on the tab itself is waking up the tab randomly, I just can't put my finger on which app/function does it.
Stremon said:
Nothing connected.
Yeah the lid has a sensor, but it does it even when I remove the cover completely or when I leave it closed and not moving.
Yes I did several factory reset, update of the firmware, and yes I'm on the latest one.
As far I can understand, a process on the tab itself is waking up the tab randomly, I just can't put my finger on which app/function does it.
Click to expand...
Click to collapse
Look for battery usage details it should tell, after having show system services ensbled
hashtowent said:
Look for battery usage details it should tell, after having show system services ensbled
Click to expand...
Click to collapse
Nothing visible there either, the app that keeps waking up the tab isn't necessarily taking any battery.
I didn't mention as it is very visible from my profile, but I'm not a beginner with android, very far from it, if I'm asking here it's because I already tried all the obvious things
I am asking if anybody has the same issue and/or was able to fix it. If not, I guess it's just my unit.
You might try this
The command like this:
adb shell dumpsys batterystats --checkin
provides a statistic for wakeups, including the reasons.
Mine wakes up. Can't figure out why either but then I'm not by any means an Android ace. I turn the screen off then after some period of time it'll turn back on. Nothing in the notifications bar the screen just turns back on for no apparent reason. So yes, it is happening to someone else but no answer as to why.
hashtowent said:
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
Click to expand...
Click to collapse
I'm sad to say that you were right, the magnetic cover was at least partially to blame for the wake events. That's a huge bummer, since I guess there is no way to fix the issue
I had this issue.
I said that notifications must not wake up the tablet and it did not appear anymore.
I know there was no notification, but it worked for me.
(in fact, sometimes, I had the impression that a notification appeared for a very short time)
LeNouveau said:
I had this issue.
I said that notifications must not wake up the tablet and it did not appear anymore.
I know there was no notification, but it worked for me.
(in fact, sometimes, I had the impression that a notification appeared for a very short time)
Click to expand...
Click to collapse
Interesting, I'll try that too, thanks
I have the plus not the pro but check if near to wake up is on under the AI Experience Center in settings.
hungmung said:
I have the plus not the pro but check if near to wake up is on under the AI Experience Center in settings.
Click to expand...
Click to collapse
Everything is disabled there.
But I am quite convinced it comes from the smartcover, as since I enterily removed it, I don't have the issues anymore and the battery lasts weeks (with light usage) instead of 2 days like before.
Issue is that there is no way to disable the smart cover magnet...
Stremon said:
Everything is disabled there.
But I am quite convinced it comes from the smartcover, as since I enterily removed it, I don't have the issues anymore and the battery lasts weeks (with light usage) instead of 2 days like before.
Issue is that there is no way to disable the smart cover magnet...
Click to expand...
Click to collapse
That is probably it. I just thought I'd offer I had similar happen and had accidentally turned that on so it was turning on every time anything moved near it.
hungmung said:
That is probably it. I just thought I'd offer I had similar happen and had accidentally turned that on so it was turning on every time anything moved near it.
Click to expand...
Click to collapse
Thanks, that indeed makes sense.
And I really wish it was just that.
I'll try again with the smart cover to see if I can do anything about it.
It's the official magnetic cover so it's a huge bummer that it causes issues...
Stremon said:
Interesting, I'll try that too, thanks
Click to expand...
Click to collapse
Hi, I was looking for a solution to the waking up of the screen. In the ¨AI Experience Center¨ there is an option called ¨automatically screen light-up¨. I turned this off, because it said that if sensor detects a face, the screen lights up, and also "other" objects can trigger this screen light up. I suppose the cover is detected while closed. Other object in the range of 0.5m can also trigger this light up. Also deactivated the notifications icons in the status bar, if not doing this, it continues to light up the screen in my P11.
Mine does the same thing...just sitting there and all of a sudden the screen lights up.
Solution:
Settings -> Display -> Lock Screen -> When to show
Turn "new notification" off